Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here are some benefits to using HTTP as a transport:</p> <ul> <li><strong>easier to get right, more likely to work in production</strong>: Yes, you will probably have to add additional dependencies to deal with HTTP (client and server side), but it's still preferable to yet another homegrown protocol, which you have to implement, maintain, care about backwards compatibility, deal with multiplatform issues (eg. endianness), etc. In terms of implementation ease, using an HTTP based solution should be far easier in the common case (especially true if you build a REST style service API for license checking).</li> <li><strong>More help available</strong>: HTTP as the foundation of the web is one of the most widely used technologies today. Most (all?) problems you will run into are probably publicly documented with solutions/workarounds.</li> <li><strong>Encryption 'for free'</strong>: Encryption is already a solved problem (HTTPS/SSL), both with regard to transport as well as with regard to what you have to implement on your end, and it's just a matter of setting it up.</li> <li><strong>Server Authentication 'for free'</strong>: HTTPS/SSL doesn't only solve encryption but also server authentication, so that the client can verify whether it's actually talking to the right service.</li> <li><strong>Guaranteed to work on the internet</strong>: HTTP/HTTPS traffic is common on the internet, so you won't run into routing problems or firewalls which are hard to traverse. This might be a problem when using your own protocol.</li> <li><strong>Flexibility out of the box</strong>: You also put less constraints on clients communicating with your server, as it's very simple to build a client in many different environments, as long as they can talk HTTP (and maybe SSL), and they know how to issue the request to your server (ie. what your service API looks like).</li> <li><strong>Easy to integrate with administrative webapp</strong>: If you want to allow users to manage their accounts associated with licenses in some way (update contact info etc.), then you might even combine the license server with that application. You can also build the license administration UI part into the same app if that's useful.</li> </ul> <p>And as a last remark (this puts additional constraints on your client side HTTPS/SSL implementation): you can even use client side SSL certificates, which essentially allow authenticating the client to the server. Depending on how you use them, client side certificates are harder to manage, but they can be eg. expired, or revoked, so to some extent they actually <em>are</em> licenses (to connect to the server).</p>
    singulars
    1. This table or related slice is empty.
    1. POimplementing server for licencing management
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USunthought
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POimplementing server for licencing management
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COSSL is totally unrelated to HTTP. You don't get any more SSL with HTTP than you get without HTTP. In fact you probably get more security without HTTP, because when you use SSL directly, you'll have to understand it at least a bit and thus stand a better chance of not doing some stupid mistake. Most HTTP libraries present their SSL options in notoriously confusing ways.
      singulars
      1. PO
      1. USJan Hudec
    2. CO@unthough! Thanks for the explanation that I like a lot..a sort of very good PRO/CONS on these usages!
      singulars
      1. PO
      1. USAbruzzo Forte e Gentile
    3. CO@JanHudec I agree that HTTP over SSL involves two distinct technologies, but from the perspective of someone building an app it's more useful to consider the combination of them as a single option because it's so common and often transparent to the server app. It's by no means the only solution, and implementing a custom socket protocol over SSL/TLS could be a better fit depending on requirements, but I'd default to something proven, well-understood, easy-to-debug, easy-to-teach (write a spec for the custom socket proto?), etc. unless I have proof that it doesn't work for my particular case.
      singulars
      1. PO
      1. USunthought
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload