search

willzeng / WikiNets

[deprecated] see cograph
https://github.com/willzeng/cograph
GNU General Public License v3.0
30 stars 11 forks source link

Make changes on the server propagate to the client #162

Closed backens closed 10 years ago

backens commented 10 years ago

Currently there is a basic warning if a user tries to save a node that has been changed by someone else in the meantime. This warning should ideally contain information about what exactly has changed, as well as an option to merge the changes.

vpontis commented 10 years ago

Moreover. This ideally should be responsive! The node should change when changed on the server.

willzeng commented 10 years ago

muttering about websockets... Should we just make a separate issue for this general problem?

Perhaps it is not worth spending too much time on the current version if we are going to switch to a better setup where database changes are pushed to the client.

On Thu, Mar 13, 2014 at 6:47 PM, Victor Pontis notifications@github.comwrote:

Moreover. This ideally should be responsive! The node should change when changed on the server.

Reply to this email directly or view it on GitHubhttps://github.com/willzeng/WikiNets/issues/162#issuecomment-37571759 .

vpontis commented 10 years ago

Yea, I think that makes sense. It'll be interesting to see what Sashko has to say about Meteor and how that could possibly help some of our problems.