Re:Peerbind: convert a webpage into a massively interconnect...
by buss on Sunday October 02, 2011 @08:21PM
(#3064494)
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!
Re:Peerbind: convert a webpage into a massively interconnect...
by Palahala on Sunday October 09, 2011 @03:45PM
(#3091144)
Nice! 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:
Re:Peerbind: convert a webpage into a massively interconnect...
by buss on Sunday October 02, 2011 @08:03PM
(#3064469)
If this is matt@, I really enjoyed the internal tech talk at the SLU campus a few months ago. During Q&A, I asked if any of this was going to be open sourced, has that changed?
Also, did you fix that javascript code execution vulnerability I found during the demo? :P
Re:Peerbind: convert a webpage into a massively interconnect...
by ______ on Sunday October 02, 2011 @11:15PM
(#3064879)
It's interesting how anonymous users just now were engaging in fun ways just by dragging -- moving the squares on top of each other, or in a line, or back in order -- without being explicitly told what to do.
Of note, node.js and Socket.IO make this kind of demo quite easy to do, if you want to do it with open technologies
Re:Peerbind: convert a webpage into a massively interconnect...
by jchrisa on Sunday October 02, 2011 @06:22PM
(#3064226)
Looks like some form of cross domain message bridge, along with some DOM code to transparently turn the messages into events. Odd that something so simple would have a proprietary server.
The latencies were fantastic, too.
If you're looking to do real-time many-user interactions on a website with minimal effort, try this!
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! ;-)
Also, did you fix that javascript code execution vulnerability I found during the demo? :P
Of note, node.js and Socket.IO make this kind of demo quite easy to do, if you want to do it with open technologies