W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

Re: Do server store arbitrary content

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Tue, 13 Dec 2005 17:46:52 -0500
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Cullen Jennings <fluffy@cisco.com>, WebDav <w3c-dist-auth@w3.org>, w3c-dist-auth-request@w3.org
Message-ID: <OFD844126C.2F9500F5-ON852570D6.007C8690-852570D6.007D205B@us.ibm.com>
OK, I'll also change my vote to "no" (:-).  The repositories I build are 
"general content" repositories, but even they have sections of the 
namespace (such as where "activities" live) which do not support arbitrary 
content.  I can see other applications (such as calendar management 
applications) which would disallow arbitrary content (or at least severely 
restrict where it can be placed).

Cheers,
Geoff


Julian wrote on 12/13/2005 05:33:28 PM:

> 
> Cullen Jennings wrote:
> > 
> > I have a questions for the WG. Can servers, within policy constraints, 
be
> > expected to store arbitrary data. What I mean be the policy 
constraints is
> > clearly a server might reject a request because it was too large, or 
it
> > decided the file had a virus and it would not store it. But in 
general, can
> > a client expect a WebDAV serve to be able to store say a HTML file?
> 
> In general, no it can't. There are servers that accept only particular 
> types of content (such as something running on top of an XML database).
> 
> Would it be useful to allow clients to discover support for these kinds 
> of things upfront? Sure, that's exactly I'd be happy to define a profile 

> and give it a compliance class name for use in the DAV header (for 
example).
> 
> Best regards, Julian
> 
Received on Tuesday, 13 December 2005 22:46:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:11 GMT