Ah, at the title I thought this was going to be about WebRTC, something I'm pretty excited about, even though it has a quite a ways to mature yet (http://caniuse.com/rtcpeerconnection).
Interesting that they left out websockets. At this point Websockets seem to be reasonably mature, and with Socket.io/Primus/etc are dead easy to use, and allow for near-real-time 2 way communication. There do appear to be some scaling issues past a certain level with websockets though, a topic I haven't been able to find too much literature about.
As for webhooks, are these more geared towards Server-to-server communication, like consuming an API on the back end? Is there any chance that in the future browsers will begin listening on our ports too?
Interesting that they left out websockets. At this point Websockets seem to be reasonably mature, and with Socket.io/Primus/etc are dead easy to use, and allow for near-real-time 2 way communication. There do appear to be some scaling issues past a certain level with websockets though, a topic I haven't been able to find too much literature about.
As for webhooks, are these more geared towards Server-to-server communication, like consuming an API on the back end? Is there any chance that in the future browsers will begin listening on our ports too?