Changes between Version 6 and Version 7 of S2S_FACADE_RESOURCE_CHANGES_R0
- Timestamp:
- 02/03/09 11:08:54 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
S2S_FACADE_RESOURCE_CHANGES_R0
v6 v7 12 12 == Task requirements == 13 13 Since this revision is the first for this task, the most important is to think out and define the way for dealing with resource changes. The core and persistence methods for this are not implemented yet, so not much can be done. Here are some things than certainly need to be finished in this revision: 14 * Think about what functionality is needed for the client in orger to deal with resource changes. 15 * In the design section, describe the decisions taken. If possible, make a visual representation of the result (diagram). 16 * In the implementation section, create an interface in org.sophie2.org.server.facade with the needed skeleton and documentation. 14 * Change manager will be developed, which will have client and server implementations. 15 * Design a Server-side change manager and change server 16 * In the design section, describe the structure of the new Manager. Make a visual representation of the result (diagram). 17 * Implement the proto version of the Manager / Server. 17 18 18 19 19 20 == Task result == 20 Source code (interface), specification .21 Source code (interface), specification (diagrams). 21 22 22 23 == Implementation idea == 23 Proposal for the methods in the interface: doChange(), undo(), redo(). 24 Since SVN clients have something like the desired functionality, you could look at the ideas implemented there. [[BR]] 25 There should be provided ways to update a resource, commit changes to the server, revert/redo a certain count of changes. [[BR]] 26 It would be good if the client updates automatically a resource to the last version every time before a commit, and the user should be notified about possible conflicts. 24 27 25 28 == Related ==