> Single-component container (MicroContainer): > Use in environments where you want to use an Avalon component > in a non-Avalon program. See my separate mail about this. > Big thing: No external metainfo. > > Embeddable Container (used to write blocks): > For things like Cocoon. This is where Fortress etc. fits in. > You have your metadata and so on, but the container is intended > to be used inside something else - Tomcat, for example. > Some external metainfo required. > > Stand alone container (used to assemble blocks): > Phoenix. Loads of metainfo.
+1. Makes sense. Note fortress should probably become a little slimmer than it is now in this setup....otherwise I'd rather keep containerkit for the common ground between phoenix and fortress, for reasons of having a speedy phoenix. But I dunno much about fortress so I might be off. Of course, we should also have: Educational Container (used to learn avalon): For people that want to "get" avalon. It is very verbose, not very safe, not for production use, but does introduce all the concepts present in fortress and phoenix (ie standalone runnable wrapper, meta information). cheers, - Leo PS: what happens to (the various pieces of) ECM and merlin? Do we wrap fortress to provide ECM's functionality, for example? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
