On 9/27/07, Julien Vermillard <[EMAIL PROTECTED]> wrote: > +1 too > > I like Dave idea, let's keep the name alive !
Then I think we need to keep aligned with the current HTTP client implementation. Shall we rename the client? According to our naming scheme, it's currently mina-protocol-http-client. What should it be renamed to? mina-asyncweb-client? Additionally, please consider we might add other protocol codecs such as FTP and SMTP. So.. I have no concrete idea on this naming issue. Any idea is appreciated! Trustin > On Thu, 27 Sep 2007 08:47:45 +0100 > "Irving, Dave" <[EMAIL PROTECTED]> wrote: > > > One thing I would add though: As we discussed (wow - it must be last > > year now probably!), it would be nice if we could keep the name alive > > (e.g. import as asyncweb?) somehow if / when this becomes a > > subproject / module of Mina. > > > > D > > > > -----Original Message----- > > From: Irving, Dave [mailto:[EMAIL PROTECTED] > > Sent: 27 September 2007 08:45 > > To: dev@mina.apache.org > > Subject: RE: [VOTE] Import AsyncWeb from Safehaus to MINA > > > > +1 :o) > > > > I cant wait to get back in to adding new features to asyncweb. It > > would be great to see the move finally take place! (Finally maybe > > I'll get a chance to do the async content streaming changes!!!!) > > > > [X ]: +1, import > > [ ]: 0, abstain > > [ ]: -1, don't import > > > > > -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
