You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Richard Emberson <re...@edgedynamics.com> on 2003/07/10 17:14:43 UTC
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: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: AW: Client Java APIs
Posted by Richard Emberson <re...@edgedynamics.com>.
Thanks for the reply.
I am considering creating a stop-gap solution; copying the
org.apache.webdav.cmd.Client, making many of the methods public
rather than package private, and rather than reading from standard
in and writing to standard out create a bunch of helper object
used as parameters to the methods and as return values.
This way I get access to all of Slide, I'd have working code
to start from, and I don't have to think too hard.
Richard
Torsten Schlabach wrote:
> 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:remberson@edgedynamics.com]
> Gesendet: Donnerstag, 10. Juli 2003 17:15
> An: slide-user@jakarta.apache.org
> 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: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
AW: Client Java APIs
Posted by Torsten Schlabach <ts...@gmx.net>.
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:remberson@edgedynamics.com]
Gesendet: Donnerstag, 10. Juli 2003 17:15
An: slide-user@jakarta.apache.org
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: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org