7 Apr 03:05
RE: The state of WebDAV Clients
jharrop <jason <at> plutext.org>
2008-04-07 01:05:46 GMT
2008-04-07 01:05:46 GMT
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 wayThe 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.
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.
>
RSS Feed