- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Fri, 10 Dec 2004 12:38:25 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: ejw@cs.ucsc.edu, "'webdav'" <w3c-dist-auth@w3.org>
>
>> This kind of thing could be useful for other applications as well.
>> It could even work with PROPPATCH, because the server knows to treat
>> this as a "per-binding" property and change only the value that
>> applies for this binding.
>
> So where do you store it? Either on the resource itself (in which case
> you need to maintain that property for each parent collection, so you
> could simply expose that information as well), or on the collection.
WebDAV servers *store* things any way they like. E.g. a new table in
the backend database called "PER_BINDING_PROPS" with column headers for
binding, property name and value. Who cares how they store it -- that's
what gives the implementors flexibility. WebDAV's model and
marshalling are what we're talking about.
>
> BTW: you seem to be changing positions frequently :-) May I remind you
> that you asked that the BIND spec mandates that properties MUST NOT
> vary across bindings?
>
As it happens, I am not changing positions on this issue (although I
reserve my right to change my mind if I'm convinced by an argument or
think of new cases). I have held this position for a year or more now
and will try to state it again another way:
That servers should be allowed to vary properties per binding and IF
that's the consensus...
then the specification should warn clients that "clients MUST be
prepared for properties that vary per binding"
ELSE IF the consensus (despite my opinion) is that properties can't
vary per binding
then the specification should say that properties MUST NOT vary
across bindings.
Lisa
Received on Friday, 10 December 2004 20:38:38 UTC