On Mon, 2008-06-23 at 20:09 +0200, Quintin Beukes wrote: ... > Is there any way to do connection management with the NIO module? I've > been looking around and can't really find a single way, other that > re-implementing the whole IO reactor class set, down as far as > ChannelEntry, AbstractMultiworkerIOReactor, etc. This is almost > reimplementing HttpCore-NIO. > > If this is true, I can jump in and modify the CVS/SVN tree, to make it > possible to do connection management, and submit the changes? >
Absolutely. However, let's discuss the high level architecture first to make sure we are all on the same page. Several projects, LimeWire and Synapse, could potentially be interested in a generic NIO connection management API and an implementation. We should take this discussion to the dev list, though Cheers Oleg > Q > > On 6/23/08, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > > On Sun, 2008-06-22 at 18:13 +0200, Quintin Beukes wrote: > > > > > I figure I'd take your advice and get this thing running for > > > Wednesday. I don't know how HttpClient does this, but I figure I'd > > > just force make a new connection on the second try :/ > > > > > > > > > Quintin, > > > > You can keep track of how low a connection has been idle and drop only > > those connections that have been idle for too long and may have been > > closed on the server side. This is what I would have done in your > > situation. > > > > > > Oleg > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
