Simply put: In REST applications, each request must contain all of the information necessary to be understood by the server, rather than be dependent on the server remembering prior requests. Storing session state on the server violates the stateless constraint of the REST architecture. So the session state must be handled entirely by the client. … Read more
I did not manage to find materials about truly RESTful streaming – it seems that results are mostly about delegating streaming to another service (which is not a bad solution). So I’ll do my best to tackle it myself – note that streaming is not my domain, but I’ll try to add my 2 cents. … Read more
I believe this is the simplest example: header := w.Header() header.Add(“Access-Control-Allow-Origin”, “*”) header.Add(“Access-Control-Allow-Methods”, “DELETE, POST, GET, OPTIONS”) header.Add(“Access-Control-Allow-Headers”, “Content-Type, Authorization, X-Requested-With”) You can also add a header for Access-Control-Max-Age and of course you can allow any headers and methods that you wish. Finally you want to respond to the initial request: if r.Method == “OPTIONS” … Read more
Query parameters are added to the URL after the ? mark, while a path parameter is part of the regular URL. In the URL below tom could be the value of a path parameter and there is one query parameter with the name id and value 1: http://mydomain.example/tom?id=1
The transport layer works using HTTP/2 on top of TCP/IP. It allows for lower latency (faster) connections that can take advantage of a single connection from client to server (which makes more efficient use of connection and can result in more efficient use of server resources. HTTP/2 also supports bidirectional connectivity and asynchronous connectivity. So … Read more
I would recommend thinking of it like you are listing multiple representations of the resource filtered by id. As such you make a GET request to the base resource: https://example.com/api/v1/products And filter the response list by id: https://example.com/api/v1/products?id=1,2,3
Do not version URLs, because … you break permalinks The url changes will spread like a disease through your interface. What do you do with representations that have not changed but point to the representation that has? If you change the url, you break old clients. If you leave the url, your new clients may … Read more
If you want to submit a POST request You have to set the “request header” section of the Firefox plugin to have a “name” = “Content-Type” and “value” = “application/x-www-form-urlencoded” Now, you are able to submit parameter like “name=mynamehere&title=TA” in the “request body” text area field
One option is to create a delete “transaction”. So you POST to something like http://example.com/resources/deletes a new resource consisting of a list of resources to be deleted. Then in your application you just do the delete. When you do the post you should return a location of your created transaction e.g., http://example.com/resources/deletes/DF4XY7. A GET on … Read more
I’ve used both of the strategies you mention. Of those two, I favor the second approach, being simpler, in use cases that support it. That is, if the versioning needs are simple, then go with a simpler software design: A low number of changes, low complexity changes, or low frequency change schedule Changes that are … Read more