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