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 | * 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. |
| 27 | * It is neccessary to design this task together with [wiki:PRO_CHANGE_MANAGER_R0], since they probably will implement same interface. |
| 28 | |