> 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. Agreed. > 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. That's the goal. So I'm : +1 for removing the crappy Sys.out.printlns. Good riddance :-) -1 for hardcoding log4j support +1 for adding new hooks if needed Remy
- Re: [httpclient] logging and testing changes Jason van Zyl
- Re: [httpclient] logging and testing changes Remy Maucherat
- RE: [httpclient] logging and testing changes Waldhoff, Rodney
- Re: [httpclient] logging and testing changes Remy Maucherat
- Re: [httpclient] logging and testing change... Jason van Zyl
- RE: [httpclient] logging and testing ch... Paulo Gaspar
- Re: [httpclient] logging and testin... Jason van Zyl
- RE: [httpclient] logging and t... Paulo Gaspar
- RE: [httpclient] logging and testing changes Kevin Seguin
- Re: [httpclient] logging and testing changes Scott Sanders
- [httpclient] [VOTE] HTTP client 1.0 release Remy Maucherat
- [httpclient] [VOTE] HTTP client 1.0 rel... Remy Maucherat
- Re: [httpclient] [VOTE] HTTP client... Jason van Zyl
- Re: [httpclient] [VOTE] HTTP c... Remy Maucherat
- Re: [httpclient] [VOTE] HTTP client... Vincent Massol
- Re: [httpclient] [VOTE] HTTP client... Scott Sanders
- Re: [httpclient] logging and testing change... robert burrell donkin
- Re: [httpclient] logging and testing ch... Vincent Massol
- Re: [httpclient] logging and testin... robert burrell donkin
- RE: [httpclient] logging and testing changes Waldhoff, Rodney
- Re: [httpclient] logging and testing changes Remy Maucherat
