Due to all lidless web requests being totally keyed on URL, not on cookies or anything similar, often we have two requests in the pipeline at the very same instant that serve the same purpose (two history requests, for instance); it's more important that we save the work on the server side than that the second request get a slightly newer set of data.
Due to all lidless web requests being totally keyed on URL, not on cookies or anything similar, often we have two requests in the pipeline at the very same instant that serve the same purpose (two history requests, for instance); it's more important that we save the work on the server side than that the second request get a slightly newer set of data.