ReachOut core framework should provide all functions required to handle the necessary network communications in an Address Family (AF) independent manner along with providing the hooks needed for module initialization and operation. The core framework should define daemon and be able to execute independent of any modules which extend the daemons ability.
ReachOut module API should provide a complete outline of the initialization and operation any given modules should implement to be compliant. Any compliant module should work with the core framework provided the API version is the same or backwards compatible. Modules themselves will be divided into seperate classes, with the initial design being for an authentication, service and database classes.
The modular design will allow for the various authentication, services and back-end server database module support to be written by various groups and organizations for various platforms and vendors allowing for a versatile client/server architecture for dynamic services.