Difference between revisions of "Persistence unified"

(Unified persistence for Eiffel)
(Unified persistence for Eiffel)
Line 2: Line 2:
 
This project is about developing a single, integrated and simple persistence framework for Eiffel.
 
This project is about developing a single, integrated and simple persistence framework for Eiffel.
  
It should be single because nothing else should be needed to access any kind of persistence services.
+
Single because nothing else should be needed to access any kind of persistence services.
  
It should be integrated because aims at integrating both the already existing technologies  and frameworks, as far as they deliver the intended benefits, and possibly new ones.
+
Integrated because aims at integrating both the already existing technologies  and frameworks, as far as they deliver the intended benefits, and possibly new ones.
  
It should be simple because it should be very easy to use, removing all the unnecessary complexity.
+
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

Revision as of 08:53, 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