NB: unrelated to TogetherJ
Mozilla Labs: TogetherJS
21–30 of 66 posts
Re: Mozilla Labs: TogetherJS
#22Looks cool! I wonder how you'd negotiate authentication with this... both users logged in presumably, you could record edit author as whoever clicked the save button (or upon each action in a "real time" saving application).
Both people are accessing the website as themselves. If one person doesn't have permission to see a page, for instance, then they won't see it. And yeah, whoever hits save is the saver ;) Doing something richer than that requires application-specific integration, which we want to support, but we also want to take cues from developers about what that should actually look like. This is one idea we have along these lines: https://github.com/mozilla/togetherjs/issues/372
Re: Mozilla Labs: TogetherJS
#23Earlier quoted context omitted.
Look here: https://togetherjs.com/docs/contributing.html#hosting-the-hu...
Note that we haven't really "finished" the story around self-hosting, so the details of this are likely to change. That's exactly what I was looking for - Thanks! It looks like they still have some documentation to fill out, but at least it's coming.
[Team member here] We haven't been very focused on the hosting story, in part because lots of people have their own requirements, and we can't predict what they are. And maybe because predicting what they are is boring. I know some hooks for New Relic have been added to the server. It's also a super-simple server that only keeps things in memory, so it's pretty darn easy to handle. Just one file: https://github.com/mozilla/togetherjs/blob/develop/hub/serve... (and only one dependency, for WebSockets).
Re: Mozilla Labs: TogetherJS
#24Earlier quoted context omitted.
It doesn't seem to be a P2P system, since it requires a server. According to the docs, "This server does not rewrite the messages or do much of anything besides pass the messages between the participants" [1] , so it's not really P2P. I'm fairly sure the Firebase requires a server too... (their server, or else they couldn't charge for it). [1] https://togetherjs.com/docs/#technology-overview
On principle we keep the server simple, echoing messages back and forth between clients. In practice it's quite hard for two browsers to connect directly to each other, and while we want to support that kind of architecture in order to get it working we still need to simulate P2P using a server.
> In practice it's quite hard for two browsers to connect directly to each other
Isn't this the problem WebRTC abstracts away? Your server should just be a TURN server (http://en.wikipedia.org/wiki/Traversal_Using_Relays_around_N...), shouldn't it?
Re: Mozilla Labs: TogetherJS
#25I want to implement a real time Collaboration editor like google docs because I want to keep data on my own servers.. Can anyone suggest me architectural points to build that...what should be stack on server side, how to send edit diffs etc..
Re: Mozilla Labs: TogetherJS
#26Looks like this would be great for customer support, and could be a nice alternative to olark. It can be configured to automatically post the invite url to another dashboard, where one of the CS execs can pick up and walk the user through.
Re: Mozilla Labs: TogetherJS
#27Video and Audio chat functionality are real advantages over other collab tools...awesome work...i will surely check this out some time..BTW is IE11 will be providing WebRTC support??
IE10 has WebSockets: http://caniuse.com/websockets – but TogetherJS doesn't support IE10 either (simply haven't been able to keep up testing with IE in addition to other browsers).
i know about websockets..actually i was asking about Web RTC which was used for Video and Audio chat here :)
Re: Mozilla Labs: TogetherJS
#28I want to implement a real time Collaboration editor like google docs because I want to keep data on my own servers.. Can anyone suggest me architectural points to build that...what should be stack on server side, how to send edit diffs etc..
Have a look at this: http://substance.io/
I'm working on something similar: https://wikidocs.com. Although our's closed source at the moment (can't say whether or not it will remain closed), we will provide a downloadable package you can run yourself.
Re: Mozilla Labs: TogetherJS
#29Seems quite similar to GoInstant.
Re: Mozilla Labs: TogetherJS
#30I want to implement a real time Collaboration editor like google docs because I want to keep data on my own servers.. Can anyone suggest me architectural points to build that...what should be stack on server side, how to send edit diffs etc..
give http://etherpad.org/ a shot