Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@synapse.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <47D1256B.4020101@wso2.com>
Date: Fri, 07 Mar 2008 16:52:19 +0530
From: "Asankha C. Perera" <asankha@wso2.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: dev@synapse.apache.org
Subject: Re: http-transport-bug fixed
References: <016d01c8803d$734f5b00$05fe01a8@IBM0618>
In-Reply-To: <016d01c8803d$734f5b00$05fe01a8@IBM0618>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit

Hi XuHongBo

I hope I got your name correctly and my apologies if I didn't..

>     I have just post a patch for 2 http-transport-bugs founded. but the patch code style is just work outside the http-core-nio  to fixe problem. 
>
> Oh.... some of the fixing code I think , should be the responsibility of http-core-nio library, so the fixed code will look like more structurable. 
>   
Cool, and thanks.. I will have a look at this and get back to you..
> Is there anyone who are familiar with http-core-nio give some advise about if we should waiting for http-core-nio library to be corrected to catch all  all network failed in sessionCallback ( now only some exception catched by sessionCallback)?
>
> Or  just like the patch code, work outside http-core-nio library?
>   
Well Oleg who is a committer of Synapse leads the Apache HttpComponents
development and I am a commiter of HttpComponents as well. So between
the two of us we should be able to get the right balance. Anyway, I will
first go through your patch and get back by early next week..

asankha

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