The HTML 5 specification and, more specifically, its Communication section defines Web sockets and server-sent events, which makes full-duplex, direct TCP communication a reality for browsers. This section of the HTML 5 specification is drawing a lot of attention. The first public draft of the HTML 5 specification was published by the W3C (World Wide Web Consortium) in January 2008, and browser vendors are already targeting certain features in the specification.

The idea of putting a full-duplex channel into the specification is not new; the TCPConnection API and protocol were initially drafted over two years ago. With recent development, in which Kaazing Corporation played a contributing role, the HTML 5 Communication section has been solidified and is now nearly complete with few, or no, additions planned. This makes it easy for browser vendors to implement native support for the Communication section of the specification, despite the full HTML 5 proposal remaining in draft form.

Three significant areas in the HTML 5 specification that impact cross-site, real-time Web development are:

1. Cross-Document Messaging
2. Server-sent events
3. Web sockets

In last post, we solved two bugs in grnotify. Now I find another bug: if you use grnotify to open google reader in your browser directly, it won't login automatically. I guess that's because google changed the login interface.

You'll find Grnotify a great tool if you use Google Reader every day. However, there are some bugs with this software even I installed the newest version that is 1.1.2.

The first problem with it is that the number of unread items will not go down to zero even when you read all the new items. The second problem is it may dead when refreshing.