W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2004

Re: [Simple] Some thoughts on XCAP's resource architecture

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 04 Dec 2004 14:00:40 +0100
Message-ID: <41B1B4F8.3060503@gmx.de>
To: Jonathan Rosenberg <jdrosen@cisco.com>
CC: Lisa Dusseault <lisa@osafoundation.org>, HTTP working group <ietf-http-wg@w3.org>, "'simple@ietf.org'" <simple@ietf.org>

Jonathan Rosenberg wrote:
> ...
>> 2a) HTTP implementation barriers.  The last HTTP server I developed 
>> would have to be rearchitected in several places to handle XCAP's 
>> interdependencies, work beyond what you'd expect from adding XCAP 
>> support.  Throughout the server, the code uses exact matching of URLs 
>> to figure out what to do -- not URL pattern matching. So for example:
>>  - The way ETags were generated and stored and changed would have to 
>> be thrown out because ETags were generated independently for every 
>> resource.
>>  - Since resources were independent, write requests for different 
>> resources could be handled concurrently with ease, but that would have 
>> to change.
> 
> 
> The proof is in the implementations; we have a few already, and those 
> folks have posted here that they havent seen these problems.

And anyway (already pointed out earlier), an HTTP server that supports 
WebDAV namespace operations already can't handle etags on a per-resource 
basis. That approach simply doesn't work.

 > ...

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Saturday, 4 December 2004 13:01:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:36 GMT