September 11, 2010
0 Comments
Trigger events to Pusher via REST
When there is an activity that you want several users to know about, your server makes a simple REST call to the Pusher API passing a JSON payload of data. This message is modelled on Javascript event triggering.
The event is relayed to the relevant browsers on the specified channel. Javascript code bound to the specified event informs the connected users of the activity.
(Link: Pusher – Realtime client push powered by HTML5 websockets, beyond AJAX)
January 4, 2010
0 Comments
I have been playing around with HTML 5 Web Sockets for a personal project. The Web Sockets API enables web browsers to maintain a bi-directional communication channel to a server, which in turn makes implementing real-time web sites about 1000% easier than it is today.
(Link: Web Sockets in Tornado – Bret Taylor’s blog)
December 25, 2009
0 Comments
So if you can’t beat them, join them. Having failed to convince others to create a better protocol, I’m now determined for Jetty to provide the best implementation of the protocol and to become the server of choice for WebSocket Comet development, deployment ( and experimenting with improving the protocol).
Jetty’s async IO architecture is ideally suited to providing a very scalable implementation of WebSocket that is well integrated with standard server-side java application environments. Thus Jetty-7.0.1 now includes a WebSocket server.
(Link: Ajaxian » Jetty introduces WebSocket support (relunctantly))
December 11, 2009
0 Comments
The Web Sockets API enables web applications to handle bidirectional communications with server-side process in a straightforward way. Developers have been using XMLHttpRequest (“XHR”) for such purposes, but XHR makes developing web applications that communicate back and forth to the server unnecessarily complex. XHR is basically asynchronous HTTP, and because you need to use a tricky technique like long-hanging GET for sending data from the server to the browser, simple tasks rapidly become complex. As opposed to XMLHttpRequest, Web Sockets provide a real bidirectional communication channel in your browser. Once you get a Web Socket connection, you can send data from browser to server by calling a send() method, and receive data from server to browser by an onmessage event handler. A simple example is included below.
(Link: Web Sockets Now Available In Google Chrome)
