WebDAV client API change

[Remy Maucherat <re...@apache.org>]

Hi,

The WebDAV client library is about to be split in two parts (the reasons for
this are given below) :
- All the HTTP/1.1 specific code is moved to the commons subproject. The
rationale is to make it easier for other projects (like Tomcat) to reuse the
code.
- The WebDAV specific part of the client library will extend that HTTP/1.1
core, and will remain in Slide.

IMO, that's the best way to keep Slide focused on its core goals (WebDAV and
content management), while allowing more people to develop the HTTP library
independently.

The API changes this causes are :
- Some classes are renamed :
  WebdavClient -> HttpClient
  WebdavException -> HttpException
  WebdavStatus -> HttpStatus
- A lot of the classes in the lib package are moved to package
org.apache.commons.httpclient

Comments ?

Note : To minimize the time needed to update any existsing application to
the new API, I can introduce some "fake" objects (for example, add back a
WebdavClient object which would directly extend the new HttpClient object).
This would almost allow full API backwards compatibility. Please let me know
if you think this would be needed.

Thanks,
Remy