Redmond: Collections Protocol Scalability

The protocol is currently schizophrenic in its approach to maintaining
orderings.  For some things it relies on direct manipulation of a
DAV:ordering property.  For others, it uses methods and headers.  Since the
value of the DAV:ordering property will be very long if the collection has
many members, direct manipulation of this property is not a very scalable
approach.  It is not a good idea to have clients use PROPFIND / PROPPATCH
on this property whenever they need to modify an ordering.  

I believe that there was consensus at Redmond to use methods for all
modifications of an ordering.  There will no longer be any mention of a
DAV:ordering property in the protocol specification.  This has the
additional benefit of allowing servers to implement ordering any way they
wish. 

--Judy


Name:		Judith A. Slein
E-Mail:		slein@wrc.xerox.com
Phone:  	(716) 422-5169
Fax:		(716) 422-2938

Xerox Corporation
Mail Stop 105-50C
800 Phillips Road
Webster, NY 14580

Received on Thursday, 25 June 1998 15:44:55 UTC