hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: HttpConnection thread-safety
Date Mon, 30 Aug 2010 13:59:33 GMT
On Mon, 2010-08-30 at 15:09 +0200, Michel Onoff wrote:
> > 
> > If that makes sense in the context of your application, go for it.
> > ReadWriteLock is available in the j.u.concurrent package. All you have
> > to do is to extend the default HttpConnection implementations, override
> > public methods and make them acquire either read or write lock prior to
> > calling the super method. 
> > 
> 
> Oleg,
> 
> this assumes that DefaultHttp(Client|Server)Connection (a concrete
> implementation) maintains no reading state that could interfere with
> writing operations and no writing state that could influence reading
> operations.
> 
> Can you confirm that this is the case, before I start with coding?
> 
> Thanks
> MO
> 

I can confirm that. Default HTTP connection implementations are
full-duplex capable.  

Source code is your best friend, though.

Oleg



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


Mime
View raw message