I have been using HiveMind now for quite a while and have come to depend
on it quite heavily on many projects - some web apps, some not. It's
features have very much improved the quality and modularity of my code.
What would prevent a user from employing Tapestry IoC as a general
purpose container like HiveMind? Would there be any benefit to building
one monolithic Tapestry jar and a set of segmented jars (something
Spring does) for more targeted use? Or why not keep Tapestry a single
project with sub-modules for IoC and the Web framework? Alternatively,
what about merging Tapestry IoC and HiveMind at some later date? It
could remain as HiveMind, or it could take on the Tapestry IoC name.
The conversations on this list indicate that key principals of both
projects intend to keep some degree of parity anyway.
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
