I don't want to hold up moving this code over. If/when we decide to put
it on a different release schedule, moving the module over to a
'commons' repo or something similar will be trivial. So, for the time
being, I would be fine if we moved asynchronous http client into MINA as
a module.
I'm eager to play with this client and I'm very eager to look into using
it to create asynchronous web service calls.
-Mike
Mark wrote:
I like Trustin's three module ideas as well. I also think Mike has a valid
concern on the release schedule. I would rather get a consensus on this
before we move forward.
On 8/23/07, Cameron Taggart <[EMAIL PROTECTED]> wrote:
I liked Trustin's three module idea:
* mina-filter-codec-http <-- common code
* mina-protocol-server-http <-- asyncweb imported here
* mina-protocol-client-http <-- AsyncHttpClient imported here
Can it be decided later, after the import, whether it should be on
the same release cycle as MINA!? Apache Felix has components such as
their "commons" on a different release schedule. I think MINA could
do the same if needed. The most important thing I think is to get the
code imported right now.
Cameron
On 8/23/07, Mark <[EMAIL PROTECTED]> wrote:
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
