What is the "opposite" of request serialization called?

Question

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?

Answer 1

I call it request piggybacking.

Answer 2

That's really just caching/memoization , with a few restrictions - some might call it result-reuse.

Answer 3

If you queue up your requests, the code waiting for the resource can examine the queue to see if there are any identical requests pending and somehow return the same resource for that one too.

Have you done any profiling? I'd bet this is way more work than it is worth.