Re: Do server store arbitrary content

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
>