Mike, I would concur with you on this. I think a sub-project of its own is good since it can be used as a standalone API (with a dependency on Mina of course). I would recommend that this API be a separate artifact from asyncweb as I think we want the client to be capable of being slit off from the server (for obvious reasons).
Jeff Mike Heath wrote: > I'm wondering where this project should really go. Do we want to make > it part of MINA (ie. put it in mina/trunk) or do we want to create a > separate subproject that depends on MINA (ie. put it in something like > mina/async-httpclient/trunk). > > I'm concerned about the agility of MINA if we start adding protocol > handlers to MINA itself. What if we make a change to MINA that breaks > one of our protocol handlers? What if there's a bug in a protocol > handler that doesn't affect 99.9% of MINA's user base? Will these > problems keep us from making releases? If we fix a major bug in MINA > that doesn't affect async-httpclient, do we still release a new version > of async-httpclient with MINA because async-httpclient is part of the > baseline MINA build? > > I would rather see async-httpclient be a subproject of MINA and have it > reside it's own directory in subversion with its own build and with its > own examples separate from the MINA examples. > > That being said, I would MUCH rather see AsyncWeb finally moved over to > MINA as a sub-project and then make async-httpclient part of AsyncWeb. > There's certainly going to be a lot of overlap between the two. We > should leverage that. > > -Mike > > Mark wrote: >> I created a mina-httpclient component on the trunk. Just working things >> out, along with an example and I will check things in. >> >> >> On 8/21/07, Mike Heath <[EMAIL PROTECTED]> wrote: >>> This sounds awesome! >>> >>> I would like to see this as the client part of AsyncWeb for two reasons. >>> First it seams to be a natural fit. Second it might give us a little >>> more incentive to finally get AsycWeb moved over to MINA. >>> >>> -Mike >>> >>> Jeff Genender wrote: >>>> Hi, >>>> >>>> First, I want to say that I am a big fan of Mina. For those who don't >>>> know me (which is everyone), I am a committer on Geronimo and have had >>>> several people ask about an async http client API to use with our NIO >>>> clients with comet for the 2.0 Geronimo server. We have had folks who >>>> want to be able to do HTTP calls to 3rd party servers from servlets/web >>>> apps to get content, and not tie up a thread while its doing its thing. >>>> So I decided to try to whip together an API that was similar to >>>> Commons >>>> HttpClient, fully asynchronous, but based on Mina...and I think I have >>>> 80-90% of it completed. It is here: >>>> >>>> http://svn.apache.org/repos/asf/geronimo/sandbox/AsyncHttpClient >>>> >>>> For what it's worth...it doesn't seem appropriate for Geronimo. So I >>>> would like to donate it to Mina. Please have a look at it and give me >>>> feed back for if I have gone down the right path. It can be enhanced >>>> greatly as this is just a start, but I think it can be very useful and >>>> become a powerful API with everyone moving to NIO. >>>> >>>> Don't hold back any comments ;-) I would really like to see an API >>>> like >>>> this and I believe Mina is just perfect for this. >>>> >>>> Please let me know what you think..and if you don't think its right for >>>> Mina..thats ok too ;-) But getting your feedback would be best for >>>> me...and making this a community project is even better ;-) >>>> >>>> Jeff >>>> >>> >> >>
