Is CoreConnectionPNames.STALE_CONNECTION_CHECK obsolete?

[Dmitry Potapov <po...@gmail.com>]

Hello,

I've tried to find if setting
CoreConnectionPNames.STALE_CONNECTION_CHECK to true introduce any
overhead when AbstractHttpServerConnection.isStale() is not called and
realized that this parameter is only read in
HttpConnectionParams.isStaleCheckingEnabled(), and this function, in
turn, is not used.
Is there any plans for marking this parameter and function deprecated?

-- 
Dmitry

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

Re: Is CoreConnectionPNames.STALE_CONNECTION_CHECK obsolete?

[Oleg Kalnichevski <ol...@apache.org>]

On Thu, 2013-03-14 at 14:17 +0400, Dmitry Potapov wrote:
> Hello,
> 
> I've tried to find if setting
> CoreConnectionPNames.STALE_CONNECTION_CHECK to true introduce any
> overhead when AbstractHttpServerConnection.isStale() is not called and
> realized that this parameter is only read in
> HttpConnectionParams.isStaleCheckingEnabled(), and this function, in
> turn, is not used.
> Is there any plans for marking this parameter and function deprecated?
> 

Hi Dmitry

This parameter is used by higher level protocol components of HttpClient
but indeed it has no effect on core components.

Everything HttpParams related has been deprecated in 4.3 including
CoreConnectionPNames. HttpCore and HttpClient 4.3 will be using newer
preference and configuration APIs based on plain Java objects.

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org