The native Slide API (org.apache.webdav.lib.*, src/webdav/client in CVS) AFAIK has a protocol-oriented and resource-oriented layer. All of the WebDAV/DeltaV/ACL/DASL/BIND functionality supported by the Slide server should be supported by the protocol-oriented layer ... but probably not by the resource-oriented layer.
The JSR-147 API (javax.wvcm.* + org.apache.wvcm.*, proposals/wvcm in CVS) is designed as an DeltaV-compliant, resource-oriented API. The implementation currently covers all of DeltaV but the advanced features (activities, baselines, etc.). Moreover, it contains not-yet-standard extensions for BIND and DASL. We have plans to add the adavanced features soon (in Slide server + WVCM). Moreover, we plan to add not-yet-standard extensions to WVCM to support ACL. The not-yet-standard extensions have been proposed to the JSR-147 Expert Group ... BIND is probable to become part of the standard soon. Regards, Peter > -----Original Message----- > From: Richard Emberson [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 10, 2003 17:15 > To: [EMAIL PROTECTED] > Subject: Client Java APIs > > > Advice/status requested. > > There appears to be three different client Java APIs in Slide: > the "native" Slide API (used by the command-line client), > the JSR-147 API (WVCM), and > the JSR-170 API (JCR). > > Which one to use? Which one gives access to the largest subset of > the WebDAV, WebDAV-ACL, and DeltaV capabilities of the Slide server? > > Thanks. > > Richard > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
