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)
