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

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

From: Joel M. Halpern <joel@stevecrocker.com>
Date: Mon, 22 Nov 2004 04:25:34 +0000
Message-Id: <6.1.2.0.0.20041121232019.03c93918@localhost>
To: Lisa Dusseault <lisa@osafoundation.org>, HTTP working group <ietf-http-wg@w3.org>, "'simple@ietf.org'" <simple@ietf.org>




I am not sure I follow all of the concerns you are raising, and I could 
easily be missing some important point.

However, we have implemented an XCAP server using an off-the-shelf HTTP 
server as a starting point.  We did not have to do significant violence to 
the HTTP code to support XCAP, the XCAP granularity, or the XCAP 
dependency.  (The places we had dependency issues had nothing to do with 
XCAP, but rather were simply that sometimes setting configuration 
information has side effects.)

We probably could also handle it if the path were moved into the 
parameters.  Hawever, the earlier discussion indicated that would not be a 
good idea.  Moving the path into a different HTTP parameter would be a very 
bad idea from my perspective.  It would be tantamount to treating HTTP as a 
transport for a non-HTTP protocol.  The fact that I can currently use a 
standard browser to get XCAP information, and a browser with PUT support 
can be used to update information is a feature, and one we should try to 
preserve.

Yours,
Joel M. Halpern

At 09:58 PM 11/21/2004, Lisa Dusseault wrote:
>During the DC IETF, I expressed some reservations about XCAP to Ted and 
>Jonathan. Jonathan asked me to send a message to the SIMPLE list with my 
>comments, so here it is...
>
>Based on the mailing list on the traffic, it appears that  XCAP is 
>supposed to be an extension or profile of HTTP, rather than just a 
>protocol that mimics the HTTP interaction style, and that as such it is 
>intended to be compatible with other extensions of HTTP.  I'm concerned 
>that the current architecture of XCAP makes this difficult.  In particular 
>the XCAP resource ontology and the URL addressing style that goes with it 
>shifts the HTTP design along two major axes:
>
>1) Resource granularity
>2) Dependency between resource
Received on Monday, 22 November 2004 14:52:42 GMT

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