REST is not a specific web service but a design concept (architecture) for managing state information. The seminal paper on this was Roy Thomas Fielding’s dissertation (2000), “Architectural Styles and the Design of Network-based Software Architectures” (available online from the University of California, Irvine). First read Ryan Tomayko’s post How I explained REST to my … Read more
I don’t think you will get a good answer to this, partly because nobody really agrees on what REST is. The wikipedia page is heavy on buzzwords and light on explanation. The discussion page is worth a skim just to see how much people disagree on this. As far as I can tell however, REST … Read more
The idea is that the response body gives you a page that links you to the thing: 201 Created The 201 (Created) status code indicates that the request has been fulfilled and has resulted in one or more new resources being created. The primary resource created by the request is identified by either a Location … Read more
I have been doing some extensive research into this and other REST paging related questions lately and thought it constructive to add some of my findings here. I’m expanding the question a bit to include thoughts on paging as well as the count as they are intimitely related. Headers The paging metadata is included in … Read more
For e.g. when a user has login.Now lets say the user want to create a forum topic, How will I know that the user is already logged in? Think about it – there must be some handshake that tells your “Create Forum” API that this current request is from an authenticated user. Since REST APIs … Read more
@ray, excellent discussion @jgerman, don’t forget that just because it’s REST, doesn’t mean resources have to be set in stone from POST. What you choose to include in any given representation of a resource is up to you. Your case of the the covers referenced separately is merely the creation of a parent resource (comic … Read more
Remember that with a REST API, it’s all a question of your point of view. The two key concepts in a REST API are the endpoints and the resources (entities). Loosely put, an endpoint either returns resources via GET or accepts resources via POST and PUT and so on (or a combination of the above). … Read more
As HTTP requests in a stateless system should be independent, the results of one request should not be dependent on a previous request. Consider what should happen if two users did a DELETE on the same resource simultaneously. It makes sense for the second request to get a 404. The same should be true if … Read more
To do that you need to leverage the “Collections” feature of Postman. This link could help you: https://learning.getpostman.com/docs/postman/collections/creating_collections/ Here is the way to do it: Create a collection (within tab “Collections”) Execute your request Add the request to a collection Share your collection as a file
Look at http.request var options = { host: url, port: 80, path: ‘/resource?id=foo&bar=baz’, method: ‘POST’ }; http.request(options, function(res) { console.log(‘STATUS: ‘ + res.statusCode); console.log(‘HEADERS: ‘ + JSON.stringify(res.headers)); res.setEncoding(‘utf8’); res.on(‘data’, function (chunk) { console.log(‘BODY: ‘ + chunk); }); }).end();