> > Well, the small problem is that this conflicts with the JAX-RS based
> WebDAV
> > implementation I am providing independent of Jersey and that I
> actually
> > wanted WebDAV to be independent of any vendor. If we would implement
> it
> > (again) with AHC, then how to be vendor independent? The only way
> would be
> > to write the WebDAV parts of the client into the JAX-RS spec to force
> other
> > JAX-RS clients to do the same.
>
> Agree. but currently all vendors have different client API right? You
> must have some kind of plugin API in your project in order to make it
> work,
The JAX-RS API defines such a plugin API for the server side, which is what
my WebDAV implementation currently is based upon (and such is vendor
independent).
For the client side, I will apply for a seat in the JAX-RS EG to get this
plugin being tailored into the API defined in JAX-RS 2.0. I do not see any
need for a different solution that that one.
Regards
Markus