With the discussion of Dave (the original author of AsyncWeb), we agreed to include the HTTP message model and codec into MINA, and make AsyncWeb focus on more high-level features like session management and proper error handling that turn a mere codec into a real world web server component. It's like AHC (AsyncHttpClient) is trying to do the same with the MINA HTTP codec.
Another extracted portion of AsyncWeb is the state machine based codec I wrote all. It's a very general codec component that can be used to build virtually any kind of protocol, so it has been included into core. The state machine based codec (org.apache.mina.filter.codec.statemachin) has absolutely no dependency on AsyncWeb. HTTP codec depends on it though. And, I personally think providing the codecs for essential protocols such as HTTP, FTP and SMTP as a part of the main MINA distribution makes a developer's life much easier when what he wants is just a minimal client / server. That's what I've been talking in ApacheCons and you can see that clearly in my slide files, which were uploaded in the official site since 2005. It's interesting that nobody argued about the road map I proposed since then. Actually we got some positive feed back related with the HTTP codec from users due to this decision. Additionally, look at our PMC charter: http://svn.apache.org/viewvc/directory/sandbox/proyal/MINA-TLP-Proposal.txt?view=markup&pathrev=437911 The idea itself about the road map was proposed since the MINA PMC is formed. We can strip down what we are doing, but I see a lot of synergy of providing some protocol codecs. Of course, this doesn't mean we have provide all kinds of protocols or high level features on top of it in the official MINA distribution. BTW providing AHC as a subproject might be a good idea - for now it's included as a MINA submodule, but we can provide it as a separate subproject. I'd like to know what Jeff thinks about it. Trustin On Jan 21, 2008 3:05 AM, Alex Karasulu <[EMAIL PROTECTED]> wrote: > Hi, > > MINA 2.0 is pushing the inclusion of specific protocol codecs into the core: > I am specifically referring to the filter-codec-http module. > > Who decided on this policy and why? Trustin, according to SVN logs you > commit this and it seems as though some of it was extracted from or overlaps > the asycweb functionality. > > What is the intention for asyncweb as a subproject if it's functionality is > being moved over to MINA core? > > Thanks, > Alex > -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
