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

Re: Some thoughts on XCAP's resource architecture

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 25 Nov 2004 08:45:15 +0100
Message-ID: <41A58D8B.2070602@gmx.de>
To: Lisa Dusseault <lisa@osafoundation.org>
CC: Alex Rousskov <rousskov@measurement-factory.com>, HTTP working group <ietf-http-wg@w3.org>, "'simple@ietf.org'" <simple@ietf.org>

Lisa Dusseault wrote:
 > ...
> It's manageable from a coding point of view, I'm sure we're all 
> excellent coders.  It's not manageable from an ease-of-use, application 
> design and GUI point of view, nor does it scale as far.  I really can't 
> think how a GUI client/user can possibly manage all the ACLs on all the 
> node resources -- the complexity is enormous if it's not scoped down 
> somehow, and if it's not scoped down now, then the natural diversity of 
> implementations will make it much harder to scope down later.

The difference is that in XCAP, you leave the decision about what 
granularity the ACLs will have to the server. It's perfectly ok if the 
server chooses to have just one for the whole document. But if it wishes 
to support a higher granularity, it can do that as well.

Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 25 November 2004 07:45:51 GMT

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