Re: Version issues
Jim Whitehead (ejw@ics.uci.edu)
Thu, 1 Apr 1999 17:05:26 -0800
From: Jim Whitehead <ejw@ics.uci.edu>
To: Versioning <ietf-dav-versioning@w3.org>
Date: Thu, 1 Apr 1999 17:05:26 -0800
Message-ID: <004f01be7ca4$e4be2560$d115c380@ics.uci.edu>
Subject: Re: Version issues
-----Original Message-----
From: jamsden@us.ibm.com [mailto:jamsden@us.ibm.com]
Sent: Monday, March 15, 1999 10:33 AM
To: Chris Kaler (Exchange)
Cc: 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; ckaler@microsoft.com;
bradley_sergeant@intersolv.com; ABabich@filenet.com
Subject: RE: Version issues
[CK2] Two points - and they represent different customer segments.
(1) This isn't my model. I have lots of unrelated documents
and, as a level 1 client app, this complicates everything.
(2) There are cases, NT for example, where workspaces will have
real scalability problems. I may want/need to manage the
state on the client not the server.
How do workspaces complicate things and for whom? I agree they make a
little more work for servers to do the revision selection, but I think it's
better to have that complexity in the server not the many clients that
access the server. You get much better reuse and simplify what clients and
users have to do. Isn't that a good thing?
Also, just because there's workspaces doesn't mean a client can't implement
its own model with labels, properties, other resource types, etc.
Workspaces aren't a restriction for clients, they're a service.