On Mon, 2006-07-31 at 10:02 +0100, Irving, Dave wrote: > > We're interested definitely! Thank you for your will for > > contribution! > > Although we need to find out the best way to cooperate with > > AsyncWeb by Dave, but I think we can get advantages from both > > sides. Great! > > This sounds very cool - Im looking forward to checking out the code! > I would suspect that the commons http stuff is far more "mature" than > asyncweb in its full http support etc. > Of course, asyncweb has the event driven model throughout which is very > useful in router / gateway style apps (b.t.w see > http://docs.codehaus.org/display/XWIRE/Home for a great example usage). > So, I think there certainly are advantages from both... It's a very > exciting time! :o)
Hi Dave, We (HttpComponents project) have started development of HTTP components that utilize HttpCore protocol code on top of an event driven I/O model based on NIO. This sub-project is presently being referred to as HttpNIO. The name of the project may change or its code base may end up merged into HttpCore. At this point all options are still on the table. I do not have an issue with AsyncWeb becoming an Apache project and competing with HttpComponents. There are many overlapping projects within Apache, so this is nothing really new. For instance, HttpComponents project itself overlaps with Tomcat Coyote efforts. Having said that I urge you to consider as an option of contributing HTTP protocol code to HttpComponents HttpNIO and building HTTP services in MINA using HttpComponents. I understand you may not be that thrilled about the idea of abandoning AsyncWeb, nonetheless, this still may be a better alternative than having two directly competing projects within Apache. Consider this as an invitation to join HttpComponents. Cheers, Oleg > > I think we're just waiting for the green light, and then asyncweb can > come to MINA - hopefully very soon :o) > > Dave > > > Trustin > > -- > > what we call human nature is actually human habit > > -- > > http://gleamynode.net/ > > -- > > PGP key fingerprints: > > * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E > > * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6 > > > > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any attachment > and all copies and inform the sender. Thank you. >
