Create centralized persistence service handling
-----------------------------------------------
Key: LABS-354
URL: https://issues.apache.org/jira/browse/LABS-354
Project: Labs
Issue Type: Improvement
Components: Vysper
Reporter: Bernd Fondermann
Different parts/extensions need persistence. These are for example: user
accounts, roster, vcard, offline messages, etc.
Implementations may rely on RDB, Jackrabbit, in-memory or CouchDB technology.
If one is exchanged for the other, it is currently required to change every
persistence service. It would be great to have only one place to change between
(for example) in-memory and JCR storage.
This central persistence service manager could be implementing the "whiteboard
pattern", where implementations don't have to choose a specific implementation,
but this is reversed: they announce their availability to a central registry
and the appropriate persistence service is provided.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
