Next message: Tim Ellison/OTT/OTI: "Review of protocol 04.3"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568CD.001F1CE4.00@d54mta03.raleigh.ibm.com>
Date: Wed, 26 Apr 2000 00:14:04 -0400
Subject: Re: Versioning TeleConf Agenda, 4/24/00 (Monday) *1-2pm*EST
Sorry I had to miss another call. I'll be back next week.
- Should we support a DAV:body property? This would support David
Goodenough's "batch fetch/update" scenario, i.e. fetching or updating
the bodies of several resources in one request.
<jra>
It seems strange to have the contents of a resource be a property too. What
would the target URL be?
</jra>
- Should we allow an activity or a workspace as the request-URL
to a CHECKIN request? This would checkin all working resources associated
with that activity or workspace.
<jra>
But if a configuration is a checked in revision of a workspace, this would
be ambiguous. These convenience methods might be useful, but I think
clients could provide the capability by iterating over the contents. This
would require more round trips, but its not clear checkin is an operation
that needs to be optimized. I'm in favor of leaving out these kinds of
optimizations until we have the core versioning scenarios and protocol
done.
</jra>