Difference between revisions of "Persistence unified"
(→Unified persistence for Eiffel) |
(→A tentative manifesto) |
||
| Line 17: | Line 17: | ||
**FORMAT | **FORMAT | ||
| − | Possible specializations of these abstractions could be: | + | Possible specializations of these abstractions could be: |
| − | + | ||
| + | **FILE_MEDIUM, NETWORK_MEDIUM, RELATIONAL_DB_MEDIUM, CUSTOM_MEDIUM, and **BINARY_FORMAT, STRING_FORMAT, XML_FORMAT, DADL_FORMAT, CUSTOM_FORMAT | ||
Revision as of 08:08, 17 August 2007
Unified persistence for Eiffel
This project is about developing a single, integrated and simple persistence framework for Eiffel.
Single because nothing else should be needed to access any kind of persistence services.
Integrated because aims at integrating both the already existing technologies and frameworks, as far as they deliver the intended benefits, and possibly new ones.
Simple because it should be very easy to use, removing all the unnecessary complexity.
A tentative manifesto
The first proposed task is to agree upon a sort of ‘manifesto’ of desirable features of the framework.
Here is a first proposal:
- The framework should provide just two abstractions to the developer:
- MEDIUM and
- FORMAT
Possible specializations of these abstractions could be:
- FILE_MEDIUM, NETWORK_MEDIUM, RELATIONAL_DB_MEDIUM, CUSTOM_MEDIUM, and **BINARY_FORMAT, STRING_FORMAT, XML_FORMAT, DADL_FORMAT, CUSTOM_FORMAT
