<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Web Socket protocol support in Java using JBoss Netty</title>
	<atom:link href="http://blog.toadhead.net/index.php/2009/12/19/web-socket-protocol-support-in-java-using-jboss-netty/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.toadhead.net/index.php/2009/12/19/web-socket-protocol-support-in-java-using-jboss-netty/</link>
	<description>Mike Heath&#039;s Blog</description>
	<lastBuildDate>Thu, 10 Nov 2011 18:05:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Mike Heath</title>
		<link>http://blog.toadhead.net/index.php/2009/12/19/web-socket-protocol-support-in-java-using-jboss-netty/#comment-37898</link>
		<dc:creator>Mike Heath</dc:creator>
		<pubDate>Fri, 29 Jan 2010 16:56:07 +0000</pubDate>
		<guid isPermaLink="false">http://swamp.homelinux.net/blog/?p=78#comment-37898</guid>
		<description>Stephen,

So the java.nio.channels.ClosedChannelException you were seeing is something I was seeing too.  I didn&#039;t take too much time to look into it.  When Trustin applied my patch to Netty, I tried out his examples and wasn&#039;t seeing any exceptions.

The exception was coming from downloading the test HTML page so I could have been doing something wrong there.  The Web Sockets side of things seamed to be working just fine.

-Mike</description>
		<content:encoded><![CDATA[<p>Stephen,</p>
<p>So the java.nio.channels.ClosedChannelException you were seeing is something I was seeing too.  I didn&#8217;t take too much time to look into it.  When Trustin applied my patch to Netty, I tried out his examples and wasn&#8217;t seeing any exceptions.</p>
<p>The exception was coming from downloading the test HTML page so I could have been doing something wrong there.  The Web Sockets side of things seamed to be working just fine.</p>
<p>-Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Bannasch</title>
		<link>http://blog.toadhead.net/index.php/2009/12/19/web-socket-protocol-support-in-java-using-jboss-netty/#comment-37620</link>
		<dc:creator>Stephen Bannasch</dc:creator>
		<pubDate>Fri, 25 Dec 2009 19:12:16 +0000</pubDate>
		<guid isPermaLink="false">http://swamp.homelinux.net/blog/?p=78#comment-37620</guid>
		<description>Hi Mike,

Thanks for sharing your websockets patch.

I haven&#039;t used netty before so this may be a silly question. 

I got netty working with your patch. When I first open the connection to http://localhost:8080 I get this error in the console:

  java.nio.channels.ClosedChannelException

Is that normal?

You can see the full console output here: http://gist.github.com/263720

I&#039;m running this with Chromium 4.0.281.0 (35262) on MacOS 10.5.8.</description>
		<content:encoded><![CDATA[<p>Hi Mike,</p>
<p>Thanks for sharing your websockets patch.</p>
<p>I haven&#8217;t used netty before so this may be a silly question. </p>
<p>I got netty working with your patch. When I first open the connection to <a href="http://localhost:8080">http://localhost:8080</a> I get this error in the console:</p>
<p>  java.nio.channels.ClosedChannelException</p>
<p>Is that normal?</p>
<p>You can see the full console output here: <a href="http://gist.github.com/263720">http://gist.github.com/263720</a></p>
<p>I&#8217;m running this with Chromium 4.0.281.0 (35262) on MacOS 10.5.8.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

