PUBLIC MARKS with tag httpput

here is the proposed sequence of steps in this scenario: clients GET the template and a token from the factory resource. since this operation does not change server state, it is safe and idempotent and it is possible to use GET. clients PUT to the token URI, at which point the server creates and populates the resource at the repository level, and keeps track of the token from which the resource has been created. the server responds with a 303 (See Other) response, indicating the persistent URI of the resource. subsequent requests to the token URIs are handled with a 301 (Moved Permanently) response, telling clients that the token URI should no longer be used, and that a persistent URI is now available.

In this article I’d like to talk more about unload event handlers, why they prevent pages from going into the Page Cache, and what can be done to make things better.