mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Irving, Dave" <dave.irv...@bankofamerica.com>
Subject RE: Asynchronous Http Client donation
Date Wed, 22 Aug 2007 13:45:35 GMT
Also, on the asyncweb front - I'm all for this still coming across and
getting integrated with this new client (sounds good). 
If enough people want it in as a sub-project (Which seems to be the
case), then it sounds like a good idea.
I really don't think much remains to be done for the integration to take
place - I just don't have the time right now to do much about it myself
:o(

However, I certainly put the hours in when it came to getting the
release grant from my previous employers (I'm sure a few people round
here will remember what a nightmare that was....) - so if someone else
has the time, and wants to pick up the gauntlet and take the final steps
to integrate it in to the mina codebase then it would be great to see
:o)
Hopefully soon I'll have more free time to start contributing properly
again!

Dave

-----Original Message-----
From: Jeff Genender [mailto:jgenender@apache.org] 
Sent: 22 August 2007 14:35
To: dev@mina.apache.org
Subject: Re: Asynchronous Http Client donation

Give me just a teeny-weeny bit more time to get the chunking code
checked in and its all yours...I'll ping the list.

Jeff

Mark wrote:
> sounds good to me.  I will work this once Mike lets me know that he
has
> everything checked in.
> 
> On 8/22/07, Trustin Lee <trustin@gmail.com> wrote:
>> On 8/22/07, Mike Heath <mheath@apache.org> wrote:
>>> Mark wrote:
>>>> Just so we are straight on terminology, what I referred to as a
MINA
>>>> component is what I think you all are calling sub-projects.  I will
be
>> sure
>>>> to get this right from now on.  These include:
>>>>
>>>> mina-example
>>>> mina-filter-codec-netty
>>>> mina-filter-compression
>>>> mina-integration-jmx
>>>> mina-integration-spring
>>>
>>> I would say that these are optional components of MINA since they
are
>>> part of the MINA build and all share the same version.  When we do a
>>> MINA release we vote on, build, and distribute all of these modules
and
>>> not just mina-core.  I don't think async-httpclient should be tied
to
>>> this process.
>>>
>>> I think a better home for async-httpclient would be to create
something
>>> like https://svn.apache.org/repos/asf/mina/async-httpclient and put
>>> 'trunk', 'tags', and 'branches' in there.  Then in trunk put a
parent
>>> pom.xml that builds the 'client' and 'examples' modules.  This would
>>> make async-httpclient totally independent of the MINA release cycle.
>>>
>>> Do others see things differently?
>> 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
>> --
>> what we call human nature is actually human habit
>> --
>> http://gleamynode.net/
>> --
>> PGP Key ID: 0x0255ECA6
>>
> 
> 
> 

Mime
View raw message