| | 55 | |
| | 56 | * provide a local change server |
| | 57 | * simulate multi-user actions if possible |
| | 58 | * get the concept about how we're going to deal with collaboration |
| | 59 | * common approach is to have remote proxy objects, when you set them and the server recieves it |
| | 60 | * instead of this, we won't have proxy objects, but real objects. We won't transfer just he values, we'll transfer changes, instead of setting the frame to 5, we'll have a change server that will collect the changes and periodically sync the changes, change server is on client and server, merges changes, this is the server that is on the client, should work without internet connectivity. |
| | 61 | * Modify resource, generates changes, change manager adds them to the change server |
