Ticket #229 (new enhancement)
obby should be a true peer to peer architecture
|Reported by:||spamfaenger@…||Owned by:||armin|
|Severity:||normal||Keywords:||p2p, obby, protocol|
when using Gobby, we often have the problem that one of the gobby-peers is the server and has to quit, while the rest of the users would want to go on editing.
This is quite annoying as the only way to achieve this is, to close the session (loosing all change marks) and reopening the document on a different peer where the others then all reconnect.
All the while it is my understanding that the basis of the obby merging algorithm was designed to work in a peer to peer environment, so it should be no problem to do this (from an algorithmic standpoint).
Several solutions come to mind:
- Promote a new server if the old one quits, so the centralised model can be retained (probably a bit less code)
- Go completely decentralized, that is, make it a peer to peer network where each gobby instance is its own 'servent' and connecting to one of the instances makes one connect to the network. This is probably a lot more work, though it seems conceptually a lot cleaner.
Well.... Thats my two cents. :)