It's the last version of Asyncweb server, running on the MINA 2.0 branch There is some new feature, like static file serving. Ashish made a perfect reply on the contribution path :)
Julien Le Tue, 21 Apr 2009 13:25:13 +0530, "Panda, Archanaa IN GGN SISL" <[email protected]> a écrit : > Thanks, what version of AsyncWeb is it in the trunk? What would be > the process of becoming a contributor for AsyncWeb? > > -----Original Message----- > From: Julien Vermillard [mailto:[email protected]] > Sent: Tuesday, April 21, 2009 1:01 PM > To: [email protected] > Subject: Re: More active Asyncweb support > > Hi, > Thanks for the feedback. > Why you don't try the current trunk version : > http://svn.apache.org/repos/asf/mina/asyncweb/trunk/ > > Asyncweb dev is stalled actually I hope to go back into it when I got > more time, but I think we badly need new (or old back) contributors > for AsyncWeb. > > Julien > > Le Tue, 21 Apr 2009 12:25:31 +0530, > "Panda, Archanaa IN GGN SISL" <[email protected]> a écrit : > > > Hello, > > > > There is I believe a large user community (including me) of mina > > which would like to see more active asyncweb development. Recently > > for one of my projects I used the safehaus asyncweb version in place > > of servlets as my architecture needed asynchronous request > > processing. This contributed (apart from other architecture changes) > > in giving major scalability - almost 10X and though it is an old > > version of asyncweb and MINA, there have been no problems I faced. > > Asynchronous request processing is a feature that would be included > > only in Servlet 3.0. Till the time it gets supported in all the > > major app servers, the java community is banking on open source > > frameworks like asyncweb, grizzly, etc for asynchronous request > > processing. > > > > Recently I downloaded grizzly source code to compare its support for > > HTTP and NIO. Grizzly is being very actively supported > > development-wise by Sun as it is the base of Glassfish. It has > > recently also ported tomcat code to enable loadbalancing and > > proxying by apache HTTP web-server. However, I found that the API > > of asyncweb is easier to use than grizzly. Hence I am not yet keen > > to switch to grizzly from asyncweb and I would like to see more > > active development in asyncweb. Now the svn repository for safehaus > > asyncweb is no longer available which is a little worrying for me > > as I don't have the source code to make bug fixes if something goes > > wrong. > > > > Like I said, I really liked the asyncweb API and would really > > appreciate if there is active development and a new release on it. > > If that is not immediately feasible, can at least the safehaus > > asyncweb source code be made available? > > > > Regards, > > Archanaa > > > > Important notice: This e-mail and any attachment there to contains > > corporate proprietary information. If you have received it by > > mistake, please notify us immediately by reply e-mail and delete > > this e-mail and its attachments from your system. Thank You. > > Important notice: This e-mail and any attachment there to contains > corporate proprietary information. If you have received it by > mistake, please notify us immediately by reply e-mail and delete this > e-mail and its attachments from your system. Thank You.
signature.asc
Description: PGP signature
