incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trustin Lee" <>
Subject Re: [pre-proposal] AsyncWeb
Date Mon, 17 Jul 2006 12:46:39 GMT
On 7/17/06, peter royal <> wrote:
> On Jul 17, 2006, at 5:31 AM, Dave Irving wrote:
> > One thing I would like to discuss though is identity....
> > AsyncWeb currently has some form of identity in its own right as a
> > project
> > (and is already bundled as a standalone http transport in a couple
> > of OSS
> > projects). Is this likely to be affected by a move to a Mina TLP?
> > E.g, Mina
> > currently has its own identity within the Directory project. Are we
> > talking
> > about a similar set up here?
> I was thinking of a similar relationship to MINA and Directory..
> AsyncWeb would *not* be renamed MINA HTTP.

AsyncWeb is a great name.  Why should we rename it? :)

One possibility though could be that MINA HTTP codec provides only encoder
and decoder implementation for HTTP messages and AsyncWeb is built on top of
it to provide more tighter integration with existing webapp frameworks and
more HTTP-friently asynchronous APIs.  Yep, this is just an imagination in
my brain.  We can talk about this step by step.

what we call human nature is actually human habit
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message