- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 29 May 2008 10:35:40 +0200
- To: Stefan Eissing <stefan.eissing@greenbytes.de>
- CC: Cyrus Daboo <cyrus@daboo.name>, Helge Hess <helge.hess@opengroupware.org>, WebDAV <w3c-dist-auth@w3.org>, vcarddav@ietf.org
Stefan Eissing wrote: > This BATCH/multi-GET topic comes up quite regularly every year or so. > It's a pony discussion. > > For all use cases I have seen so far either > 1. pipelining was adequate for it > 2. or examples where as you described with optimizations for multiple > operations (security checks, dbms lookup, etc.) > > Case 2 could be betterh andled (e.g. without changing the worldwide HTTP > implementation) by optimizing the URL namespace. What I mean is that one > adds URLs to the application which represent specific views on multiple > resources. Those you can then retrieve with a single GET. > ... Right. Actually, my proposal allows a server to assign a GETtable URI to any REPORT response, so a client would have an extremely simply way to find out about the URI. BR, Julian
Received on Thursday, 29 May 2008 08:36:23 UTC