Question

Closed. This question needs to be more focused. It is not currently accepting answers.

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed 4 years ago.

I m wondering what the technologies and best practices are behind real time collaboration in web interfaces.

An example of this is of course Google Wave. Another is PivotalTracker.com.

I m particularly interested in any work (frameworks, plugins, etc) people are doing with Ruby on Rails here.

I imagine it would have to use Javascript underneath at some level, but you would need a way to abstract this out. Probably polling the server periodically to see if changes have been made, and also a way to resolve conflicts if in the middle of editing something the server comes back and says someone else has updated it.

Thank you!

Answer 1

Wave has operational transform that has a nice property of being easily combinable. You have two users, each of them does "something" in the user interface and two "somethings" can be combined into final document. That allows you to skip the problems with conflict resolution.

A nice way to enable real-time updates to state of the app is by using Comet, which is essentially a geeky codename for keeping an alive, long standing, unterminated get/post request to the server, that server finishes and responds to when something happens on the server. It allows sending to the client instantaneous updates without having the client periodically poll.

I can t really say how to abstract this away in javascript/r n r, many of the underlying technical details are hard enough and application specific that no framework supports them out of the box.

友情链接