Regarding the NIO connection management, if there is, just a general overview, a finger pointing in the right direction would be sufficient. I'll figure out the rest, and ask if I truly get stuck.
Q On 6/23/08, Quintin Beukes <[EMAIL PROTECTED]> wrote: > Hey, > > That is a great idea. I was actually postponing parsing the Keep-Alive > header until later. Had I not done that I would have probably never > run into this problem :> > > I'm almost finished with the project anyway. This was the biggest > problem so far. Probably be finished tomorrow night or early > Wednesday. HttpComponents saved me some seriously large amounts of > hours!! > > 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? > > 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] > > > > > > > > -- > > Quintin Beukes > -- Quintin Beukes
