We had hoped that using miles to decide would approximate the performance of using hops. Server-initiated caching is most efficient when overhead operations, such as pushing documents, are minimized. Servers should therefore push multiple pages. We had expected that pushing many pages at a time would be more efficient than pushing a few pages at a time because it would amortize the overhead of push-caching over more pages. This question is outside the domain of this work, so we used the simplest method suggested by Blaze and discussed in section .
Clients contact the original server on first request.
The server may then send the client a redirect message instructing it to use a different cache instead. Using a more efficient location scheme can only improve the performance of push-caching. If not, it simply returns the document. If so, it sends the client a redirect message for each of its documents currently cached at that server. This policy is designed to minimize the number of server queries necessary, amortizing the cost of querying a distant server over the many local requests that are thereby made possible.