Re: [httpclient] logging and testing changes

[Scott Sanders]

> > Ok, I can understand why we would want to have integrated logging as a
> > convinience feature for the application. However, I'd like to have the
> > client go into no logging by default, and have the application use the
> > interceptors to log what it wishes to log. I believe the current
> > interceptors should be enough for that task (but we can add
> > additional hooks
> > if it's not the case).
> >
> > What do you think ?
> >
>
> as a (hopefully) future user of httpclient, i'd certainly like to not have
> to download and use log4j with httpclient.  i'm probably plugging
httpclient
> into an existing application, with existing logging stuff (not log4j) and
> the plugable logging approach would be much better for me.
>
> just my $0.02 :)
>

I am a current user of http-client, and I also use log4j in the same
project.  But I would rather see the interceptor approach taken, because my
use of http-client needs to be completly transparent to the application
administration.  This is indeed the way to go, and I intend to push digester
in this direction as well.  It can afford the same level of functionality,
while allowing the end user more control.

Scott Sanders