Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: pass (nike.apache.org: domain of asankha.apache@gmail.com
 designates 209.85.220.54 as permitted sender)
Sender: Asankha Perera <asankha.apache@gmail.com>
Message-ID: <5110E574.8060100@apache.org>
Date: Tue, 05 Feb 2013 16:26:52 +0530
From: "Asankha C. Perera" <asankha@apache.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: HttpComponents Project <dev@hc.apache.org>
Subject: Re: Question on HC Connection pooling - PoolEntry
References: <510CB602.7030704@apache.org> <1359831274.20832.9.camel@ubuntu>
In-Reply-To: <1359831274.20832.9.camel@ubuntu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Oleg
>> public synchronized void updateExpiry(final long time, final TimeUnit
>> tunit) {
>>           Args.notNull(tunit, "Time unit");
>>           this.updated = System.currentTimeMillis();
>>           long newExpiry;
>>           if (time > 0) {
>>               newExpiry = this.updated + tunit.toMillis(time);
>>           } else {
>>               newExpiry = Long.MAX_VALUE;
>>           }
>>           this.expiry = Math.min(newExpiry, this.validUnit);
>>       }
>>
> Hi Asankha
>
> Let's say a pool entry is created at 10:00 with the total time to live
> of 10 minutes. The validUntil value is set to 10:10. Let's say at 10:05
> #updateExpiry takes 10 minutes as input thus making newExpiry equal to
> 10:15. Should not validUntil still apply and take precedence over
> newExpiry?
>
> Oleg
That's what I was wondering, and I thought the newExpiry should take 
precedence, since each time I re-use a connection, I'd typically want to 
extend its life time. I guess re-using connections is my objective when 
using a connection pool, and thus, with each re-use the life time should 
extend, unless some request causes a connection close or non-reusable 
event where its discarded.

When I created the original connection I state that it can be reused 
within another 10 minutes - i.e. until 10:10. When I do re-use it at 
10:05, if I am to call updateExpiry() again, that indicates that I want 
to now "update" the expiry time which is currently set. Now if I say I 
want to re-use this again in the next 10 minutes, i.e. until 10:15, the 
new expiry time should be the max of validUntil and newExpiry

thanks and regards
asankha

-- 
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com


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