On Fri, 2007-02-09 at 18:58 +0100, Roland Weber wrote: > Hi Oleg, > > > I proposed a Java5 specific module be created in HttpCore to contain NIO > > SSL stuff and a few adapter classes for java.util.concurrent interfaces. > > Apparently the idea was not well received by Roland and I have not heard > > any strong opinions in favor of it from other committers. So, we are > > kind of stuck. What do we do now? What are the alternatives? > > I meant to have this discussion after alpha4 is out, but since delaying > it would cause you unnecessary work, here is my dubious (TM) plan: > > - we have a component that is virtually dead at the moment: HttpAsync > - nobody but me ever cared to make a distinction between async and NIO > => > a) archive the contents of HttpAsync in SVN for future resurrection > (I would like to have the archived code compile against alpha4) > b) move HttpCore-NIO to HttpAsync-NIO, partially or in total > (can wait until after the alpha4) > c) put the NIO-SSL code in a new module-java5 in HttpAsync > (can be done right away) > f) resurrect current HttpAsync as module-dispatch or HttpDispatch > (depending on how we want to manage the release cycles) > > What do you think? > > cheers, > Roland >
Hi Roland, My only reservation about the wholesale move of NIO extensions to HttpAsync is that we already let it out into the wild as an official HttpCore release. I would very much welcome HttpAsync becoming a set of services intended to simplify NIO programming, and I am very much favor of moving (almost) everything that has to do with the protocol layer from HttpCore NIO to HttpAsync, ThrottlingHttpServiceHandler for instance. Could you live with that? 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]
