On 5/10/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
<snip>
As an example in the past days I've heard people saying they want to make JCR *THE* api between modules: this is a change that IMHO cannot live together with the old style in the same build tree.
provided that care is taken over packaging naming, yes it can JAMES has a lot of modules that work ok and work on java 1.4: there is no reason why the code needs to be replaced. provided that new package names are chosen, the new code can live beside the old.
The handlerapi experiment also require changes in the socket/protocol handling core so all protocol functions would be interested by such a change in the core. Again this new "module" could not live together with the old module.
provided the code is factored correctly and the build is modular, it can the abstract socket/protocol handlers should be factored into libraries. functions should depend on whatever libraries they require. when factored in this fashion, new and old implementations can life side-by-side. i would really like to see the experimental handlerapi stuff moved into trunk as a socket library, protocol layer and experimental function. this would require some repackaging of some code in the branch but i don't see why this should be a major issue. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
