Internet Communication

Hiya there! HTTP is a platform where everything magical happens but its also stateless. But with the help of RESTful API, we can now implement a system where we can send a request to execute requests on end-points. Request is simply an object literal containing all kinds of information, like what kind of request of it is including payload, or headers etc. Mostly request can be either GET or POST. GET is simply for fetching something from resource. Whereas POST is for adding some data to the resource. But there are actually 4 requests types. And other types are PUT/PATCH and DELETE. PUT is simply for updating something which already exists on resource, whereas DELETE is, as name suggests, deleting something from the resource.

Now, most of the time you'll only encounter either GET or POST. But in real world applications, you're gonna have to implement a back-end for all 4 requests types and response for the same request types. Now, response mostly contains status code, the format you asked for (like it can be json or xml or fragments of HTML etc.), messages and headers. Im pretty sure you've stumbled on to a uri something like this:

www.example.com/articles?id=2&&author=John

Now, see the pattern after ? (question mark), this is what we call Payload. Payload is simply the addtional information provided by the user in order to perform query on the resource. In above uri, its a GET request. How do i know that? Simply coz only GET request contains payload/query string in the uri. Whereas POST request contains sensitive data , which gets sent in the body of request object. BTW when i say resource , i mostly mean the database or Model layer or View-Model.

~ Ari