commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: The state of WebDAV Clients
Date Mon, 26 Nov 2007 15:42:35 GMT
Hello Chris,

> JackRabbit does not currently have a WebDAV client implementation
> according to this post
> (

The way I read this post, they have the implementation.
It is just not released as a separate component.

The released version of the Slide WebDAV client is
based on HttpClient 2.0, which has been unsupported
for years. It also includes contrib code from
HttpClient which was never supported in the first

> I think it is clear that there is a need for
> a project like this.

That is good to know.

> Has there been any though in starting an Apache
> Commons project to provide WebDAV support?

Not as a Commons project, but it was discussed
as a part of HttpComponents. The most recent
discussion took place on general@jakarta:

We made sure that the scope of the new
HttpComponents TLP allows for releasing
a WebDAV client, whether that is based on
Slide or Jackrabbit or something else. But
projects depend on volunteers to do the work.

> My understanding was that the Slide client was
> stable and would probably provide a good starting
> point for a WebDAV client.

It has no unit tests, no developer community,
and is based on an HttpClient API scheduled
for replacement. The Jackrabbit WebDAV client
is also based on an HttpClient API scheduled
for replacement, but it has a developer community.
I don't know about their unit tests.

> For more information on my WebDAV research see this post:

Thanks for the pointers. I may post a comment on
your blog later this week. For now: we did not retire 
Slide because Jackrabbit is a perfect replacement.
We retired Slide because it had no developer
community that could address a security vulnerability:

Oliver made a fix in Subversion, but there was
nobody who could release a fixed Slide, either
as a minor update to the last Slide release years
ago, or as a new release of the current code in
Subversion. Projects that cannot address security
vulnerabilities need to be retired. This does not
depend on the availability of an alternative. It
depends only on the availability of a developer

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'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.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message