Changes between Version 2 and Version 3 of S2S_PERSIST_ARCHIVING_R0

Timestamp:

02/03/09 12:19:20 (16 years ago)

Author:

kyli

Comment:

--

S2S_PERSIST_ARCHIVING_R0

@@ -7 +7 @@
 
 == Overview ==
-Different kind of resources are going to be persisted on th Sophie2 server - users, books, etc. For now, resources are stored in a database. We should not allow this database to be bloated, so a way for cleaning it up must be defined.
+Since the server will use the base persistence module, it is going to use the same persistence schema. Having in mind that the server will store every resource change, the persisted information will certainly be too much. 
 
 == Task requirements ==
-Design and implement a model for S2S database archiving. Think about the following aspects:
+Design and implement a model for storage archiving. Think about the following aspects:
  * Archiving old resource changes.
  * Dealing with old comments.
  * Archiving unused accounts. [[BR]]
-Make decisions on these and apply them to the org.sophie2.server.persistence layer.
+You must also revise the current persistence of changes - is there a way to store less data without affecting the performance of the change manager. For this, it is good to implement this task together with the ones, concerning about changes. [[BR]]
+Make decisions on these and apply them.
 
 == Task result ==
-Source code - extra features in org.sophie2.server.persistence.
+Source code.
 
 == Implementation idea ==
-1st: Implement this task after (or together with) [wiki:S2S_PERSIST_CHANGES_R0]. The problem here is that this task is in the next revision. [[BR]]
+1st: Implement this task together with the PRO_CHANGE tasks (they are too much, so they will not be listed here). [[BR]]
 2nd: Think out just the mechanism for archiving, apply it to the currently persisted objects. Changes' shrinking can be implemented with the next (main) revision.
 
@@ -31 +32 @@
 
 == How to demo ==
-
+Show the code, run the tests (if any).
 
 = Design =