Richard, let's ask in the fist place what is implemented where.
AFAIK JSR-147 and JSR-170 are not (yet) implemented in the Webdav client library that comes with Slide. And I do not know of any other open source Java Webdav client library. In fact, I am mostly using the client portion of Slide and as it is my feeling that the development team is much more interested in the server piece, I'd rather switch if I'd find a project where they put more effort in the client. I was thinking of helping out by for example authoring a client programming HOWTO (I found it to be much less intuitive than I would have though in the first place) but as is was my impression for far that there are few Slide users that are interested in the client I was not sure if my time was well spent. On the other hand it appears to be much more difficult to make a Webdav client library interact with different servers and handle things such as (authenticating) proxy servers and the like very well. Also, I know of at least one severe interoperability issue when it comes to using the Slide Webdav client library to access a Tomcat Webdav servlet on the server side. Ask me for details if you're interested. Torsten -----Urspr�ngliche Nachricht----- Von: Richard Emberson [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 10. Juli 2003 17:15 An: [EMAIL PROTECTED] Betreff: 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
