What is the "opposite" of request serialization called?

Posted by Adam Lindberg on Stack Overflow See other posts from Stack Overflow or by Adam Lindberg
Published on 2010-04-20T22:46:00Z Indexed on 2010/04/20 22:53 UTC
Read the original article Hit count: 314

For example, if a request is made to a resource and another identical request is made before the first has returned a result, the server returns the result of the first request for the second request as well. This to avoid unnecessary processing on the resource. This is not the same thing as caching/memoization since it only concerns identical requests ongoing in parallel.

Is there a term for the reuse of results for currently ongoing requests to a resource for the purpose of minimizing processing?

© Stack Overflow or respective owner

Related posts about request

Related posts about serialization