Sorry for the spam, but effectively it seems to be related to a change in
the protocol because I've just tried the Jetty 7.1.4-SNAPSHOT (which
supports both versions of the protocol) and my local code started working
again.
-Tako
On Tue, Jun 8, 2010 at 00:44, Tako Schotanus <tako_at_codejive.org> wrote:
> Aha, I just found this on the chromium blog:
>
> http://blog.chromium.org/2010/06/websocket-protocol-updated.html
>
> Could possibly be related because I just found out that the things that
> worked before (those that I mentioned before) have all suddenly stopped
> working as well. Probably a browser update snuck me by without noticing.
>
> -Tako
>
>
>
> On Mon, Jun 7, 2010 at 22:28, Tako Schotanus <tako_at_codejive.org> wrote:
>
>> Hi,
>>
>> I mentioned this already on Justin Lee's blog (
>> http://www.antwerkz.com/glassfish-web-sockets-sample) but I haven't been
>> able to get the websocket chat sample to work with the latest Glassfish 3.1
>> (downloaded June 2nd).
>>
>> First I tried to just re-create the needed files from the information on
>> his blog and when that didn't work out I just downloaded the latest grizzly
>> and built the entire thing copying the websocket chat sample WAR to the
>> Glassfish autodeploy folder. Although much better looking than the version I
>> threw together the result stayed the same. A strange error from Chromium
>> about needing a helper application (see attached image).
>>
>> It's not a problem with Chromium as far as I can see because many of the
>> sample on the net function without any problem, as well as samples that I
>> have running locally using jWebsocket and Jetty.
>>
>> Cheers,
>> -Tako
>>
>> PS: Just curious, but the Websocket implementation that Jetty uses (a
>> WebSocket is a subclass of HttpServlet) seems conceptually a bit simpler
>> than the way it's done in Glassfish (using both a WebSocket and a
>> WebSocketApplication). Any particular reason as to why?
>>
>
>