Re: Alternative webdav client api?
Good initiative :) Eirikur S. Hrafnsson Chief Software Engineer Idega Software http://www.idega.com On Apr 7, 2008, at 1:12 AM, jharrop wrote: Roland Weber wrote: Is there a natural migration path for my situation? If all you use is the client, there is no immediate hurry. However, the Slide WebDAV client is based on an unsupported backlevel version of HttpClient, besides being unsupported itself. As long as it works, you're fine. As soon as a problem occurs, you're on your own. The Jackrabbit WebDAV client is your best option at Apache. I don't know about any non-Apache WebDAV clients. I've uploaded the slide webdav client code to https://sourceforge.net/projects/webdavclient4j where it can be maintained/enhanced as necessary. I've replaced the unsupported HttpClient with the newer 3.0.1 client. -- View this message in context: http://www.nabble.com/Alternative-webdav-client-api--tp13885439p16532022.html Sent from the Jakarta Slide - User mailing list archive at Nabble.com. - 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]
Re: Alternative webdav client api?
Roland Weber wrote: Is there a natural migration path for my situation? If all you use is the client, there is no immediate hurry. However, the Slide WebDAV client is based on an unsupported backlevel version of HttpClient, besides being unsupported itself. As long as it works, you're fine. As soon as a problem occurs, you're on your own. The Jackrabbit WebDAV client is your best option at Apache. I don't know about any non-Apache WebDAV clients. I've uploaded the slide webdav client code to https://sourceforge.net/projects/webdavclient4j where it can be maintained/enhanced as necessary. I've replaced the unsupported HttpClient with the newer 3.0.1 client. -- View this message in context: http://www.nabble.com/Alternative-webdav-client-api--tp13885439p16532022.html Sent from the Jakarta Slide - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Alternative webdav client api?
We have found the slide client to be stable and free of issues. I would not immediately assume that it is not a good option because the development effort has been retired. Alon On 11/21/07, Florian Kirchhoff [EMAIL PROTECTED] wrote: Hi, the retirement announcement for Slide, mentions Jackrabbit as an alternative to slide. I am mostly interested in using the api to access an existing WebDav repository, but it seems Jackrabbit is mostly focused on the server side of webdav, not the client. Is there a natural migration path for my situation? Thanks in advance for any help, Florian -- View this message in context: http://www.nabble.com/Alternative-webdav-client-api--tf4852654.html#a13885439 Sent from the Jakarta Slide - User mailing list archive at Nabble.com. - 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]
RE: Alternative webdav client api?
Hi, the retirement announcement for Slide, mentions Jackrabbit as an alternative to slide. I am mostly interested in using the api to access an existing WebDav repository, but it seems Jackrabbit is mostly focused on the server side of webdav, not the client. Is there a natural migration path for my situation? There are already some mails about this on the jackrabbit user list. I think you have a better chance of getting help on that list, Regards Ard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Alternative webdav client api?
Hello Florian, the retirement announcement for Slide, mentions Jackrabbit as an alternative to slide. I am mostly interested in using the api to access an existing WebDav repository, but it seems Jackrabbit is mostly focused on the server side of webdav, not the client. That is correct. But they do have a WebDAV extension to HttpClient. Besides, Slide was also mostly focused on the server side :-) Is there a natural migration path for my situation? If all you use is the client, there is no immediate hurry. However, the Slide WebDAV client is based on an unsupported backlevel version of HttpClient, besides being unsupported itself. As long as it works, you're fine. As soon as a problem occurs, you're on your own. The Jackrabbit WebDAV client is your best option at Apache. I don't know about any non-Apache WebDAV clients. cheers, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
