RE: The state of WebDAV Clients

2008-04-06 Thread jharrop


Roland Weber wrote:
 
 Users of the current Slide codebase are welcome
 to fork and support the code. They are even more
 welcome to form a new project to move away from
 the HttpClient 2.x/3.x API.

I've uploaded the slide webdav client code to
https://sourceforge.net/projects/webdavclient4j  where it can be
maintained/enhanced as necessary.  

The new name is intended to convey that this can (or rather, will, depending
on contributions) interoperate with a variety of webdav servers.



  I'm willing to invest
 some effort into that next year, after we've
 completed the HttpComponents move to TLP. But
 at the moment, I don't see too many people working
 on a WebDAV client. If you know any, please send
 them our way :-) The best starting point for now
 would be the Jackrabbit client code that is just
 waiting for somebody to release it.
 
 Of course you can always continue to use the
 Slide WebDAV client. There wasn't much support
 for some time, so the situation didn't really
 change by the retirement. It is now just obvious
 to anybody that the code is unsupported.
 

-- 
View this message in context: 
http://www.nabble.com/The-state-of-WebDAV-Clients-tp13950123p16531993.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?

2008-04-06 Thread jharrop


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]