4 ms·
This was demoed to Amazon developers internally, and is immensely cool. The main demo involved having all of the developers pull up the slideshow on their lapto
by buss 15y ago
This was demoed to Amazon developers internally, and is immensely cool. The main demo involved having all of the developers pull up the slideshow on their laptops, and everyone's instance of the slideshow followed along with matt's instance (when he advanced a slide, we all did automatically).
The latencies were fantastic, too.
If you're looking to do real-time many-user interactions on a website with minimal effort, try this!
- Palahala 15y agoNice! Any chance you know if (and where) we can report issues? One possible issue: It seems that binding to the same peer-event multiple times, also SENDS all outgoing events multiple times. For example, open the example website peerbind.com and then run: $('#chatinput').peerbind("change", { peer: function(e) { console.log("Incoming", e.peerSrc, e.peerData); } }); Now, by simply binding to incoming events twice, everything one sends in the chat, is sent twice too. I guess that's not the expected behavior? Still, nice! And for those who agree that the chat example is not very secure: peek into the HTML source for the actual implementation! ;-)
- mamacker 15y agoGood find! Thanks, I'll take a look. If you see anything else wrong - feel free to send me a note: matt@a9.com