On Fri, 2007-02-09 at 21:40 +0100, Roland Weber wrote: > Hi Oleg, > > > 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. > > That's cool. I wasn't sure whether you'd like to split the module. > I didn't have a problem with the initial module-nio in core, I just > feel that it has accumulated too much functionality later on. >
Roland, At the moment HttpCore is significantly ahead in development compared to other modules, hence the tendency to shove more stuff into it to make sure it gets released sooner. As HttpClient and HttpAsync start to catch up, things will get back to normal. > If you start putting the new code in module-XXX directories, we > can leave the old async code in there until alpha4 is out. That > will make it easier to archive a version that compiles with a4. > So, can you live for the time being with 3 impl classes in HttpCore NIOSSL: an IOSession SSL decorator and two SSL aware event dispatchers? We can deprecate HttpCore NIOSSL at the same time with the first ALPHA release of HttpAsync. You will not have to add it to the Ant build. I'll be taking care of those three little buggers. Oleg > happy hacking, > Roland > > --------------------------------------------------------------------- > 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]
