What a choices here are my ideas about this: The term application and module can be seen in terms of architecture.
-Modules, provide an service (sending mail , converting images,scheduling). to have any benefit from using modules modules typically have interfaces to access them modules should not depend on other modules. modules will typically have multiple implementations available. -Applications on the other hand are higher level things that typically will use several modules and will require special selections of modules to make them work. a typical user installing an application will want to see something nice and easy -the core at present is one big configurable module with api stacked on top of each other making it difficult to introduce new services(like an alternative bridge api using bridge level nodemanagers) I would like to see something like this for modules contrib/security/cloudcontext contrib/security/aselect contrib/database/generic contrib/database/mssql contrib/database/oracle contrib/workflow/api contrib/workflow/wiab contrib/email/jms contrib/email/smtp contrib/imageio/dummy contrib/imageio/jmagick contrib/imageio/imagemagick contrib/imageio/jai api/security/api api/security/tests api/imageio/api api/imageio/tests api/email/api api/email/tests api/database/api api/database/tests api/versioning/api api/jsrXXX/api and I don't really care about full applications but they should just have there own cvs module since they will not have the same relase cycle _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
