On Sun, 2007-01-28 at 10:18 +0100, Roland Weber wrote: > Hi folks, > > where do you feel is the best place for keeping the > ConnectionReuseStrategy? > > 1. attribute in the connection manager > 2. attribute in the HttpClient > 3. stored in HttpContext, allows per-request override > a) default as attribute in connection manager > b) default as attribute in HttpClient > c) default hard-coded (never reuse) > 4. stored in HttpParams, allows per-request override >
I tend to prefer 2. I am strongly not in favor of storing interfaces in HttpParams. CredentialsProvier was my biggest design blunder in the HttpClient 3.x days. Why would you want a different connection re-use strategy on a per request basis in the first place? Oleg > Should we have a NoConnectionReuseStrategy implementation > of the interface in HttpCore? > > cheers, > Roland > > --------------------------------------------------------------------- > 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]
