On 7 Feb 2004, at 19:33, Nevermann, Dr., Peter wrote:
do you think that in the future we might be able to use wvcm instead of the client library?
Sure. I mean, the impl is in an advanced state. Almost all of what is specified in the public review version (end of 2003) is done. Still missing are mainly 2 things:
1. Support for deltav advanced features (merge, activities, baselines and versioned colls) ... mainly because these are missing in the Slide server impl too :)
2. Local resource proxies are missing.
I think I need to explain local proxies a little bit. In WVCM you use resource proxies (interface "Resource" and sub-interfcs) to operate on a resource (read/write props/content, checkout/-in, bind/unbind, etc.). Resources have a "Location" which mainly wrappes the URL. Typically, a resource proxy is sort of a handle for a resource on the server and it's location typically is something like http://myhost:8080/slide/files/foo. Now, WVCM defines local proxies to represent local copies of resources to support e.g. working offline or client-side workspaces. A local proxy's location typically point somewhere to the local filesystem, e.g. file://fs4711/files/foo. WVCM defines some mechanics for synchronizing between the local and the server proxies.
do you see any drawbacks?
No. WVCM has already been used in a couple of projects at my company. To be honest, some of my colleagues complained a little bit about WVCM as they think it takes getting used to. The reason maybe is that WVCM intentionally has been kept rather simplistic ... I my be biased, but think it is coherent.
I think that if we started using Slide as a testbed for both 147 and 170 it would also help defining them better as we go.
We did this for the servlet API with JServ and it worked very well. Things were not so corporate at that time, but hey, as long as we have the same goals, things work out just fine in my experience.
-- Stefano.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
