On Jan 20, 2008, at 11:42 PM, Trustin Lee wrote:
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?
i propose something different../mina/(trunk|tags|branches) - core, examples, transports, statematchine
/http/(trunk|tags|branches) - filter-codec-http, protocol-http- client, asyncweb
/ftp/(trunk|tags|branches) - ftpserver (and a separate codec if its desired to fragment it some
a few key points: * no protocols in the "core" (/mina) * generic filters only in the "core"* organize based on "functional area" .. i think having /codecs/ is wrong, its too broad. if we get a bunch of mail-related code, we can create /mail, and put them all in there. * i agree that HTTP code does not belong in the core, and that asyncweb should not be languishing in the sandbox.
-pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
