The document discusses WebSocket and Comet technologies for real-time web applications. It begins with an overview of WebSocket protocols and how they enable two-way communication between client and server. It then contrasts WebSocket with Comet, which uses HTTP for real-time updates. The remainder discusses Socket.io, an abstraction layer that allows real-time applications to work across WebSocket and Comet. It highlights features like automatic fallback, namespaces, storing data, and broadcasting in Socket.io.
2. NTT
Twitter http://twitter.com/komasshu
Blog http://blog.livedoor.jp/kotesaki/
HTML5
Google API Expert(HTML5)
Microsoft Most Valuable Professional(IE)
11 8 28
7. WebSocket
The WebSocket protocol
draft-ietf-hybi-thewebsocketprotocol-10
Abstract
The WebSocket protocol enables two-way communication
between a client running untrusted code running in a
controlled environment to a remote host that has opted-in
to communications from that code. The security model used
for this is the Origin-based security model commonly used
by Web browsers. The protocol consists of an opening
handshake followed by basic message framing, layered over
TCP. The goal of this technology is to provide a mechanism
for browser-based applications that need two-way
communication with servers that does not rely on opening
multiple HTTP connections (e.g. using XMLHttpRequest or
<iframe>s and long polling).
ref) http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-10
11 8 28