This is an old revision of the document!
This page is designed to capture ongoing discussion about possible moves to a new framework on which to base the next version of Sahana.
High Level Requirements
The requirements section is designed to capture the high-level desires and requirements.
Following is a list of requirements we look for in a new framework. Please add anything that you feel require.
- ORM,
- - Connection Pooling Support, so that multiple access doesn't create a database connection bottleneck
- - Data versioning, Audit trail support
- Form Validation, Error/ Exception Handling
- Database Abstraction
- Web Services SOAP/ RSS / REST
- Security / Auditing
- Logging, Backup
- Strong Web2.0 Support (Builtin JQuery, Mochikit, Xajax etc etc)
- Easily integratable with existing Portal Frameworks, such as Yahoo Pipes, iGoogle. ( I think this would go with web services & REST) (Optional)
- Mobile Device Support (Optional)
- Easy installation and deployability, easy to customize
- Less bulky.
- More modularity with low coupling.
- MVC ?
- Should we go with SOA ?
- Scalability and performance.
- Large developer ecosystem - e.g. choose a well supported framework
- Less complex framework, so that the learning curve is minimized, hence will reduce the customization time by new users/developers in immediate deployments.
- Unit Testing of framework for assurance that underlying platform has suitable quality
- Strong geospatial capabilities
Framework Options
These are sorted alphabetically.
- Django (Python)
- Drupal 7 (PHP, no decent web link yet)
- ezComponents (PHP)
- GeoDjango (Python)
- Symfony (PHP)
- web2py (Python)
- Zend Framework (PHP)
