2007/8/10, Roland Weber <[EMAIL PROTECTED]>:
> Oliver Zeigermann wrote:
> > Martin's and
> > also my hopes had been that when the - indeed useful - WebDAV client
> > was moved to a different project it could actually be revived. Reasons
> > are that it is functional, useful and of much less complexity than the
> > server. I would at least volunteer to support the initial move
> > (including cleanup) to HttpComponents and once it is there am
> > confident it will attract further contributors. The command line
> > client should be dropped, really.
>
> So the idea would be to leave the server part behind and
> just cut out the WebDAV client based on HttpClient 3.x
> during the move?
> HttpClient 4.x has no API similarity to 3.x at all,
> so it is inevitable that the WebDAV client be ported
> to the new 4.0 API if it's supposed to have a future.
> Content related parts should be re-usable, but everything
> on the method level will need to be re-written.

Got that.

> Moving Slide, or the WebDAV client from Slide, is one
> option. Another option is to leave Slide and it's 3.x
> based WebDAV client behind and just start with a new
> WebDAV client based on the 4.0 API in the new project.
> That would significantly reduce the administrative
> overhead and does not preclude code re-use from Slide.

Maybe that could be a second step.

> While I would like to get rid of HttpClient 3.x rather
> sooner than later, there's no denyig that it will stay
> with us for several years to come. From this angle, it
> would make sense to move the WebDAV client as it is.

Maybe that could be the first step.

WDYT?

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to