Difference between revisions of "Persistence unified"
(→Unified persistence for Eiffel) |
(→Unified persistence for Eiffel) |
||
Line 3: | Line 3: | ||
It should be ‘'single’' because nothing else should be needed to access any kind of persistence services. | It should be ‘'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. | 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. | ||
− | It should be | + | It should be ``simple`` because it should be very easy to use, removing all the unnecessary complexity. |
Revision as of 08:20, 17 August 2007
Unified persistence 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. 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. It should be ``simple`` because it should be very easy to use, removing all the unnecessary complexity.