Details
-
Task
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
I see some module is really small (seda) while other modules are really big (codec). I graphed the package dependency tree (it is a tree only after grouping the 2 cycles above) and it resulted that the codec module have 2 separated hierarchies:
http://people.apache.org/~bago/imap/graph-imap-full-package-check-no-torque.gif
Does it worth splitting? (note that imap.message.request.base+imap4rev1 and imap.command.imap4rev1 can be moved in both "groups").
3b) maybe we could even shorten package names: codec.encode => encode and codec.decode => decode
3c) another option would be to extract the imap.message package to its own module (message). codec (or both decode/encode if it is splitted) would then depend on this message module). If I'm not wrong processor would so depend only on "message" and not on codec(decode/encode).