Goal: Actually there are 2 goals:
- Be able to only deploy the desired features of Xplanner
- Better support for extending Xplanner functionality
This is somehow related to the REFACTOR Architecture Layering idea. Xplanner features could be developed and delivered as plugins (modules, whatever the name) that depend on a common core. The core would implement a mechanism for deploying/loading plugins. Example of plugins:
- data access (layer)
- identity management
- metrics (potentially multiple, independent plugins)
- support for notifications (email)
- support for web-services (SOAP)
- support for calendaring (iCal)
A thorny problem would be plugins dependency.
