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

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]

Reply via email to