Wednesday, October 29th, 2008
>Comet is starting to gain steam, although mainly through the term “real-time Web.” A couple of the Comet folks posted at the same time, both talking about the technology in different ways.
Ted Goddard answered a bunch of questions in WebSocket is neither Web nor Socket.
- Does WebSocket use TCP ports 81 and 815?
- How does WebSocket make use of an HTTP connection on port 80?
- Does WebSocket obey the same origin policy?
- Is WebSocket restricted to the two-connection limit of HTTP?
- Can WebSocket read and write arbitrarily as with low-level socket APIs?
- How does WebSocket delineate messages?
- How are function call semantics implemented over WebSocket?
- Is WebSocket easy to implement?
- Can we just upgrade HTTP?
Michael Carter had a fun little spin on things in HTML5 WebSocket and WebJneering.
I want to tell you about HTML5, specifically about the advances in bi-directional, asynchronous communication. But I’m troubled. Consider two propositions that I didn’t come up with: 1) Nothing is new, 2) Everything Sucks. Let these simple truths cast a shadow upon the tale you are about to read…
HTML5 provides a new thing called a WebSocket. I’m pretty sad that its not a TCPSocket, but alas, it was easier to throw in a handshake for security than to set up some out-of-bound security method, such as flash’s cross-domain policy files. We can’t connect to existing TCP servers, so we’ll just have to start over and write new WS/TCP servers. No problem. WebSocket will still be our salvation, leading us towards our stateful future.
Both Michael and Ted will be joining myself, Alex Russell, Dylan, John Fallows, and others at an event tonight in Mountain View covering Comet. If you are in town, join us!
We are using the Google Moderator to help answer questions you want heard, so
add your questions too.
Posted by Dion Almaer at 10:18 am