> > > Why not: > > > > > > /stuff.json?depth=1 > > > > > > It's not like we need to use the URI mapping for everything. > > because this breaks caching. > > Really? I'm probably out of touch with current practice in HTTP > caching, but at least in theory there should be nothing in query > parameters that would prevent caching.
but in real life. for example when a form input is used to display search results. so the content of the resulting page changes if the underlying search space changes. and since not all apps use proper cache prevention (like no-cache headers etc.) most proxies do not cache requests with a query (at least afaik). in any case, i find it a very good and simple differentiator (beside the common http headers) to decide whether to cache responses or not. and i would keep it this way in sling. regards, toby -- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
