Sounds like a plan..

Thanks.

> -----Original Message-----
> From: Oleg Kalnichevski [mailto:[email protected]]
> Sent: Monday, July 19, 2010 3:26 PM
> To: HttpClient User Discussion
> Subject: Re: 4.0.1 -> 4.1
> 
> On Mon, 2010-07-19 at 14:27 -0400, Brooks, Kenneth S wrote:
> > Both of these are now deprecated in 4.1 with a message of Do Not Use.
> >
> >         ConnManagerParams.setMaxTotalConnections(...);
> >         ConnManagerParams.setMaxConnectionsPerRoute(...);
> >
> > Is there a suggested alternative?
> > I was under the assumption that this would set the number of
> connections in a pool.. Maybe that was a bad assumption.. what exactly
> is that driving and is there and alternative?
> >
> 
> Take a look at
> 
> ThreadSafeClientConnManager#setMaxTotalConnections and
> ThreadSafeClientConnManager#setMaxsPerRoute
> 
> There has been a number of complaints about misuse of HttpParams for
> things that do not need parameter hierarchies. This is the reason why
> HttpParams based connection pool configuration have been deprecated in
> favor of simple setters and getters on the ThreadSafeClientConnManager
> class.
> 
> Oleg
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law.  If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED.  Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
 If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.

Reply via email to