Mohammad, http-common is planned to have no library dependencies of what so ever (barring rt.jar and jsse.jar). We have even done away with commons-logging. My suggestion is to consider using DI (dependency injection) pattern, not a particluar DI container. Ideally, should DI be chosen over SL, http-common should be compatible with DI mechanism of popular IoC containters. That's it.
We all agree we do not want configuration file(s). HttpParams will remain the HttpClient's only configuration mechanism. Cheers, Oleg On Wed, May 18, 2005 at 10:15:36PM -0400, Rezaei, Mohammad A. wrote: > Two comments: > > 1) It would be preferable to keep the library dependencies to a minimum. I > don't necessary want to deploy hivemind.jar if I'm using spring or vice > versa. > 2) Whatever you end up choosing, there has to be programmatic (as opposed to > file based) way to configure the set of services required to use httpclient. > > Thanks > Moh > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
