Re: one more "Greg issue" :-)

> What do you need these properties for?

Essentially, DAV requires some "batons" to be remembered and passed
back to it in order to operate. We could synthesize the values from
available information by picking a convention (the activity could
probably be some fixed string relative to the repository, and the
version resource could be synthesized from the URL and version in the
entries file), but that would be another place where we'd be breaking
compability with other DeltaV servers.

It's a tricky problem. I'd certainly be happier if the network layer
could operate without keeping any extra state between operations, but
that doesn't seem possible for DAV/DeltaV. (At least, not
efficiently; presumably you could get ahold of appropriate version
resources by performing some sequence of queries.)
Received on Sat Oct 21 14:36:18 2006