JSON VS. XML

  • JSON is smaller, faster, simpler syntax and easier parsing.
  • XML is stricter and has support for schemas ans namespaces.
    • schema support: the ability for party A to specify the format of a document, and the ability for party B to check that they are supplying something that matches this format.
    • the ability to mix data intended to be read by multiple sources (or written by multiple sources) in the same document.

What is the difference between laas, paas and saas?

What’s the difference between a compiled and interpreted language?

In HTML forms, what’s the difference between using the GET method versus POST?

  • If a "GET" request is used, the form parameters are encoded in the URL in what is called a query string. The form parameters can be anything, and in the example we gave earlier they would be the username and password for your email provider. Here’s an example of the query string that would be generated if we were to use a "GET" request:

      www.someemailprovider.com/[email protected]&password=xxyz

    In the GET request above, you can see that the form parameters (login and password) are attached to the end of the URL itself. Note that defining a login form to use the GET request method – as we did in this example – is a very bad idea. This is because people logging in will see their passwords being displayed in the url and may be led to think that your site is not secure. One should almost always use a POST form whenever passwords are involved, for other reasons that are explained below.

    A POST request, unlike a GET request, passes the form parameters in the body of the HTTP request, not in the URL. This happens behind the scenes, in what can be thought of as an HTTP ‘dialogue’ between your web browser and a webserver.

  • The main thing to keep in mind as a programmer is that defining your form to use the GET method does not protect against causing changes. You could use a GET request to do pretty much the same thing as a POST query. It’s just that browsers are generally coded to expect that POST requests will be used for things that will cause changes – like placing an order, or writing to a database, etc . GET requests should be used for pure queries that don’t affect anything on the server. So, one should always remember not to use GET requests for any action that would cause a change on the server – like ordering a big screen tv.

  • HTML GET VS. POST