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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
