the main page and requesting the embedded objects for example it is up to the particular implementation of a web browser in which order embedded objects are requested the same holds true for objects manifesting themselves as a result of executing other embedded objects since in principle the proxy server 204 may know which web browser a client 202 is using the proxy server 204 can adjust its prefetching policy accordingly to better match the subsequent sequence of requests from the client 202 while the prefetch actions occur the client 202 may remain in the doze state for a longer period and occasionally wake up to determine if there are packets queued up at the proxy server 204 once the main page is retrieved by the client 202 it is very likely that the client 202 stays in the awake state until it has received all currently released objects from the proxy server 204 and that this time interval tawake is significantly shorter than in the non proxy configuration as the embedded objects are served from the local proxy server 204 cache furthermore the client 202 will return to the doze state soon after the last object is retrieved since the client 202 can be configured with a low ttimeout value as packet transfers occur across the low latency client proxy connection the client 202 must be configured programmed or wired to detect the presence of the.