Rodney Waldhoff wrote:
> It may make sense to someday (maybe someday soon) move the WebDAV methods
> into HTTP client, maybe as an add-on or optional package/JAR.
>
> This might actually make it easier to help keep Slide in sync with HTTP
> Client--if we can clearly distinguish the public interface (i.e., the
> methods used by Slide) from the private one (i.e., the way in which the
> HttpMethod implementations make use of HttpMethodBase), we could change the
> "back-end" and not the front and Slide wouldn't be inconvienced at all.
>
> The WebDAV methods would also provide additional examples of HttpMethod
> implementations, and may be useful outside of Slide anyway (perhaps a client
> that needs to interface with a WebDAV server?)
>
> Anyone from the Slide team care to weigh in?
Actually, the Slide Client does very well with other WebDAV servers.
Moving the WebDAV client code to common makes it easier to keep in sync with
HttpClient but makes it harder to keep in sync with the WebDAV server code.
The some WebDAV specs are still in draft and are changing...
The Slide release will include a version of HttpClient, Slide 1.1 will include
HttpClient 0.9 or something like that.
Download slide and you get everything you need to connect to a WebDAV server.
We could make a separate binary release with only the client libs if needed but
the complete package isn't that large.
Dirk
