PUBLIC MARKS with tag Websocket

The tricky bit was figuring out where the phones are – GPS just isn’t accurate enough. I was inspired by the Junkyard Jumbotron – it puts markers on each phone, then you take a picture of them all. But in my app a marker would be way too small so instead I use a unique sequence of flashes.

Pusher is a Push Notification service that uses Websockets for relaying messages back and forth between clients.

ArduinoWebsocketClient, an Arduino client for connecting and messaging with Websockets

Pusher is a centralized service that allows you to distribute real-time events from your web apps to the browser using HTML5 WebSockets.

Pour rappel, WebSocket est un nouveau protocole, standardisé par IETF et inclus dans HTML5.

Sauf que la version WebSockets de l'IETF n'est pas exactement la même que celle de HTML5. D'ailleurs quel HTML5 ? Celui du W3C ou celui de la WHAT Task Force ?

Based on quotes from Google and Firefox blogs.

You can loose server side events under the following conditions:

• long-polling: between reconnection, servers side events may happens and if they aren’t persisted, those events will never reach your client.
• websocket: Websocket are new and most if not all firewall will close them after some X idle times. Again, all server sides events will be lost
• http-streaming: Some proxy really don’t like the http-streaming technique, and will close it right away. Again, possibility to loose server sides events.
• Unexpected network outage: the connection can also be closed by something between your browser and server.

Je pense qu'il ment pour WebSockets, Hixie n'aurait pas pu laisser passer une telle déficience, il est infaillible et tellement pragmatique.