- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 17 Nov 2008 22:21:49 +0100
- To: Werner Baumann <werner.baumann@onlinehome.de>
- CC: ietf-http-wg@w3.org
Werner Baumann wrote: > ... > Additionally the response to a PROPFIND request is highly client > defined. With three levels of DEPTH and about 10 properties defined in > RFC 4918, there are about 3000 different possible responses for the same > state of the same resource. And clients are free to create any number of > custom properties. Nothing an intermediary cache would like to cache. > > Apart from the method the intermediary cache would have to include the > DEPTH header and a list of requested properties into the key. And what > would be the cache hit rate? > ... It could be quite good, depending on what clients do; such as refreshing a collection view over and over again (think explorer-like clients). BR, Julian
Received on Tuesday, 18 November 2008 14:45:57 UTC