Hi,
I've rewrote the sample chat application and I'm happy to say it looks like
working even if it's only on my own machine for now.
The downside is that when I open two tabs in Chrome and connect to the chat
in each tab and then close single tab both of the WebSocket get closed on
the server side, and then on the client side as well.
I have the sample application in git repository at
http://github.com/ido-ran/NWebSocket-Client it's the YASO directory.
Another thing is that I've notice if I leave the chat after login idle for 5
minutes the socket get closed. Is it client side or server side close it? Is
there a way to tell on the server side if the socket was closed due to
server side or client side ?
Thank you,
Ido
On Mon, Jul 26, 2010 at 2:27 PM, Justin Lee <justin.d.lee_at_oracle.com> wrote:
> What's out of sync with what? I ran chat sample last week, I believe.
>
>
> On 7/26/10 4:33 AM, Ido Ran wrote:
>
>> Hi,
>> I'm glad to see that there is yet another change(s) to the web-socket
>> implementation.
>> The problem is that the sample chat application is not out-of-sync with
>> the
>> latest code.
>> Is it possible to either explain the changes
>>
>> (NetworkHandler</source/browse/grizzly/trunk/code/modules/websockets/src/main/java/com/sun/grizzly/websockets/NetworkHandler.java?rev=4770&view=log>
>>
>> related)
>> or sync the sample code?
>>
>> Thank you very much,
>> Ido
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>