Re: [Exist-development] httpclient issues

[Loren C. <lor...@gm...>]

Hello Dannes,

I do not have any problem with implementing a WebDAV client function module.  I am planning on implementing all of the HTTP methods for WebDAV client.  I can implement the PROPPATCH as webdav:proppatch().  I just need to get it implemented.

I could copy the code from the library and implement it myself, but I have a timeframe issue.  I can first implement webdav:proppatch() with the jar and then change over to our own code.  I just have to get something implemented this week.

Loren


On Aug 16, 2010, at 12:35 PM, Dannes Wessels wrote:

> Hi,
> 
> 
> Hmm the log() dependency, that is a strange one... what is happening there?
> 
> What is the idea of having a PROPPATCH method? What about the other webdav METHODS like PROPFIND? Is it a good idea to have webdav specific functionality in a generic HTTP client?  WebDAV is HTTP but HTTP is not  WebDAV.... are you sure both map on each other well enough?
> 
> If you want to implement a webdav client, maybe we need to have a different module, specific for Webdav? 
> 
> 
> On 16 Aug 2010, at 18:30 , Loren Cahlander wrote:
> 
>> There is also another issue.  The commons-httpclient-3.1.jar has been superseded with the HttpComponents project http://hc.apache.org/.
> 
> version 3.x has been the primary library for a long time. Until 6 months ago or so, the 4.x release was not good usable for production. Good that things change over time :-) Adam has experience with the 4.x release in our attempt to introduce jsr-225 aka xqj.
> 
> 
>> What should be our plan of attack?
>> I would like to add the downloading of the webdavlib-2.0.jar in the building of the httpclient extension module so that I can get the PROPPATCH method implemented.
> 
> Why? I estimate that the PROPPATCH layer is very thin, I would vote against another library with limited added value. I guess it can be coded ourself easily. Or ultimately copy some code from an other distribution?
> 
> 
>> We can then discuss HttpComponents and Axis2.
> 
> Sorry i don't see the relation with axis2; upgrading axis to axis2 does imply lot's of work [check of dependancies etc], and probably some risks. Not sure what the added value is compared to 'the costs'. And we have the SOAPserver which is a better powerful interface....
> 
> Kind regards
> 
> Dannes
> 
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
> 
> 
> 
> 
> 
> 
> 
>