Okay. Then it's time for restructuring. (Excited :) We have
ftpserver, AHC and Asyncweb. FtpServer and AsyncWeb are under
sandbox, but I think FtpServer is mature enough to bring it up to the
subproject right away because Niklas G is working on the project and
Niclas Hedman told me it's pretty mature project.
So... I'd like to suggest the following directory structure:
/ - mina - trunk
- tags
- branches
- ahc - trunk
- tags
- branches
- ftpserver - trunk
- tags
- branches
Does it make sense, or would you suggest better structure?
Also we could give some nicer name to AHC. What about Superluminal?
(http://en.wikipedia.org/wiki/Faster-than-light)
Cheers,
Trustin
On Jan 21, 2008 4:13 PM, Jeff Genender <[EMAIL PROTECTED]> wrote:
>
>
> Trustin Lee wrote:
> >
> > BTW providing AHC as a subproject might be a good idea - for now it's
> > included as a MINA submodule, but we can provide it as a separate
> > subproject. I'd like to know what Jeff thinks about it.
>
> +1...I like the idea of it being a sub project ;-)
>
>
> >
> > Trustin
> >
> > On Jan 21, 2008 3:05 AM, Alex Karasulu <[EMAIL PROTECTED]> wrote:
> >> Hi,
> >>
> >> MINA 2.0 is pushing the inclusion of specific protocol codecs into the
> >> core:
> >> I am specifically referring to the filter-codec-http module.
> >>
> >> Who decided on this policy and why? Trustin, according to SVN logs you
> >> commit this and it seems as though some of it was extracted from or
> >> overlaps
> >> the asycweb functionality.
> >>
> >> What is the intention for asyncweb as a subproject if it's functionality is
> >> being moved over to MINA core?
> >>
> >> Thanks,
> >> Alex
> >>
> >
> >
> >
>
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
