Next message: Edgar Schwarz: "Re: DAV:revisions property for a workspace resource"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568C5.0049903F.00@d54mta03.raleigh.ibm.com>
Date: Tue, 18 Apr 2000 09:23:25 -0400
Subject: Re: DAV:revisions property for a workspace resource
Edgar,
Go ahead and implement versioned collections! I didn't mean it would be
hard for you, just some of the rest of us :-)
> <jra>
> There was talk in the original WebDAV spec a couple of years ago to send
> deltas. Unfortunately, this is resource type dependent, and difficult to
> put in the protocol without requiring changes to the protocol standard to
> support new resource types. Clearly this is unacceptable. It is also not
> clear that this optimization is required given the level of traffic and
> frequency of updates in an authoring environment.
> </jra>
Why do you need a new resource type ? There are very simple byte based
delta descriptions which would be shorter in any case than PUTing
the whole new version and doing a checkin afterwards.
Just send the data as application/octet-stream and you are done.
<jra>
You don't need a new resource type for the deltas, but the server has to
calculate the deltas. Its this calculation that is different for each
resource type. So introducing a new resource type would require a change to
the Delta-V spec to include how the deltas are transmaitted for that type.
</jra>