I was one of the people who were involved in bringing AHC over from the Geronimo sandbox (where it was first developed) to under asyncweb. Originally it was based on mina 1.1.x as at that time mina 2.0 was still in its active development. We did the bare minimum to make it compile against mina 2.0 (but not necessarily all the runtime correctness), and merged them. It landed at the org.apache.ahc package to avoid confusion with the pre-existing client code that was under org.apache.asyncweb.client. The intention has been that not only would we make it work correctly with 2.0, move to a common codec, subsume the existing client, etc. but also would redesign the client. Unfortunately, the momentum stalled because key people who were most interested in making this happen (myself included) didn't get to make the big push. For me, my involvement was cut down for reasons that are unrelated to the project.
Some discussion threads that may be of help: http://tinyurl.com/djr4pa http://tinyurl.com/azbpzg http://tinyurl.com/dkrlzv http://tinyurl.com/csonsf Having said that, I'd love to see this get going again (although my bandwidth on this is still quite limited). I'd certainly be happy to contribute what I can... As a side note, there is a "working" version of the asyncweb client in the 1.0 branch. This is almost the original version that is based on 1.0, and I think it is of production quality (we're using it in production). It hasn't seen an official release however. But please note that I don't think we will (or should) support this in a serious manner. Instead, we need to focus our effort on the trunk version based on mina 2.0. My 2 cents. Thanks, Sangjin On Mon, Mar 2, 2009 at 8:34 AM, Jacob Tomaw <jacob.to...@gmail.com> wrote: > Emmanuel, > > Your caution is understandable. The only code change for the server is > setting up the MINA LoggingFilter, but clearly there might be changes in > MINA from M3 to M4 that affect the server in an unknown way. > > I am very interested in improving AsyncWeb (at least the client portion). > My company is in the process of upgrading out 85+ application (no idea how > many JVMs) to use AHC to communicate with each other. > > Is there someone already attached to the project who has a deep knowledge > of > AsyncWeb and has a direction they would like to see the project go? Right > now there are to clients in the client dir and it is not clear what should > happen with the two of them and if any more transitioning need to take > place. > > Thanks, > Jacob > > On Fri, Feb 27, 2009 at 11:25 AM, Emmanuel Lecharny <elecha...@apache.org > >wrote: > > > Jacob Tomaw wrote: > > > >> I see that this is happening because the client is not completely moved > >> from > >> the ahc structure to the asyncweb.client structure. It is also not > using > >> the common codec. > >> > >> I am prepared to open jiras and create patches to clean this up. > However, > >> I > >> want to gauge the likelihood of these patches being integrated into the > >> trunk. I see several jiras with ptches attached and not further > comment. > >> Neither acceptance or rejection. > >> > >> > > Hi Jacob, > > > > it's just a matter to find people interested in improving AsyncWeb ! I > will > > have a look at the patches, and try to get them applied. However, I have > a > > very shallow knowledge about AsyncWeb code base, so I'm afraid it can > break > > the server... > > > > > > Thanks ! > > > > -- > > -- > > cordialement, regards, > > Emmanuel Lécharny > > www.iktek.com > > directory.apache.org > > > > > > > > > -- > Jacob Tomaw > tfl:The Flatiron Life (http://tomaw.com) > Follow me on Twitter! (http://twitter.com/JacobTomaw) >
