based on Mike's comments, I am not sure where we want to go with all this. On 8/22/07, Jeff Genender <[EMAIL PROTECTED]> wrote: > > Mike and Mark, > > I did my final commits. Feel free to grab the code. I will hold on > further development until it hits the Mina repo. You can find it all > here: > > http://svn.apache.org/repos/asf/geronimo/sandbox/AsyncHttpClient/ > > Thanks, > > Jeff > > Mike Heath wrote: > > Trustin Lee wrote: > >> We might be able to extract common codec from both server and client > >> side into a separate module and let two depend on it, resulting three > >> submodules in total: > >> > >> * mina-filter-codec-http > >> * mina-protocol-server-http > >> * mina-protocol-client-http > >> > >> wdty? > >> > >> Trustin > > > > Are you suggesting making the above sub-modules part of MINA itself? I > > don't like this idea as stated in my previous messages. I don't like > > tying the release of MINA to the release of HTTP protocol handlers and > > vice versa. > > > > I very much like the idea of extracting common functionality between an > > HTTP server and HTTP client and having both the client and server depend > > on the common module. > > > > After giving it a lot of thought, I'm of the opinion more now than ever > > that we should make async-httpclient part of AsyncWeb. They have too > > much in common to keep them separate IMO. There's no reason that > > AsyncWeb should be a server only project and IIRC, there were plans made > > a while ago to create a client for AsyncWeb. Such a move would also > > give us a good incentive to finally get AsyncWeb migrated over to MINA. > > > > WDYT? > > > > -Mike >
-- ..Cheers Mark
