Re: Version issues
Jim Whitehead (ejw@ics.uci.edu)
Thu, 1 Apr 1999 16:59:35 -0800
From: Jim Whitehead <ejw@ics.uci.edu>
To: Versioning <ietf-dav-versioning@w3.org>
Date: Thu, 1 Apr 1999 16:59:35 -0800
Message-ID: <003c01be7ca4$139ba200$d115c380@ics.uci.edu>
Subject: Re: Version issues
-----Original Message-----
From: Chris Kaler (Exchange) [mailto:ckaler@exchange.microsoft.com]
Sent: Thursday, February 25, 1999 9:30 AM
To: 'jamsden@us.ibm.com'; gclemm@atria.com; ejw@ics.uci.edu;
dgd@cs.bu.edu; Cragun.Bruce@gw.novell.com;
sridhar.iyengar@mv.unisys.com; bradley_sergeant@intersolv.com;
ABabich@filenet.com
Subject: RE: Version issues
<jra2>
Sure. But I'm still stuck on how a server will distinguish multiple working
resources checked out from the same revision.
</jra2>
[CK]One way is to have a checkout token which identifies each checkout.
Then the server doesn't have to care -- it has a way to separate them.
I don't know that the server wants to care about organizing checkouts
as a general rule. Workspaces, I think, are a mechanism that servers
provide to help the client organize their work (views and checkouts).
So what I'm saying is that workspaces provide a great abstraction on
the store to help clients manage complexity. However, clients may have
their own way of managing complexity and fundamentally, the server is
really just managing a set of revision graphs.