Mogul, J. et al. RFC 3229: Delta encoding in HTTP. IETF RFC.2002.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....modems operating at roughly 33.6 Kbps. For our purposes the most important features of the WebTV trace are: # itreflectsactivityinacacheless system, i.e. both browser and proxy caches were disabled during data collection; # the clients never used HTTP features such as Ranges or Delta encoding [38], so every reply body is self contained; and # it contains anonymized message digests of every reply body. The last feature is crucial to the present investigation, for it illuminates the relationship between a URL and the data payload returned as a result of a specific access to that URL at a ....

J. C. Mogul, B. Krishnamurthy, F. Douglis, A. Feldmann, Y. Y. Goland, A. van Hoff, and D. M. Hellerstein. RFC 3229: Delta encoding in HTTP, Jan. 2002.

....operating at roughly 33.6 Kbps. For our purposes the most important features of the WebTV trace are: # it reflects activity in a cacheless system, i.e. both browser and proxy caches were disabled during data collection; # the clients never used HTTP features such as Ranges or Delta encoding [38], so every reply body is self contained; and # it contains anonymized message digests of every reply body. The last feature is crucial to the present investigation, for it illuminates the relationship between a URL and the data payload returned as a result of a specific access to that URL at a ....

J. C. Mogul, B. Krishnamurthy, F. Douglis, A. Feldmann, Y. Y. Goland, A. van Hoff, and D. M. Hellerstein. RFC 3229: Delta encoding in HTTP, Jan. 2002.

No context found.

Mogul, J. et al. RFC 3229: Delta encoding in HTTP. IETF RFC.2002.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC