RE: [platform-vcm-dev] The WVCM API

[Steve K Speicher <sspeiche@xxxxxxxxxx>]

From: Geoff Clemm

      No, JSR-147 does not provide any WebDAV protocol functionality, but
      rather its semantics were defined to be compatible with those of the
      WebDAV/DeltaV protocol, so that an implementation could use the
      WebDAV/DeltaV protocol to communicate with its server.

      So a particular implementation of the WVCM API could chose to use the
      WebDAV/DeltaV protocol to communicate with its server, and could use
      the Eclipse WebDAV component to do so.  But alternatively, a WVCM API
      implementation could use Web Services, RPC over TCP/IP, or even just
      use a shared network file system to store the "server state".


Thanks for the information Geoff.  I was a little confused by the wording
in JSR-147, section 2.1 where it says:
   This specification will address these problems by defining a client side
   library that will expose the full DeltaV functionality and will use the
   DeltaV protocol to communicate with a server.

Then in section 2.5 it says:
   All communication between the client library and the server that
   provides the versioning and configuration management services will be
   done over the DeltaV protocol, which is an application of the HTTP/1.1
   protocol.

So JSR-147 just defines DeltaV-like semantics.  I just found the above
wording to be a little confusing, maybe its just me.  Its been known to
happen before ;-)

- Steve