Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Updating Socket.IO
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Nate  
View profile  
 More options Mar 4 2012, 5:03 pm
From: Nate <morse.n...@gmail.com>
Date: Sun, 4 Mar 2012 14:03:11 -0800 (PST)
Local: Sun, Mar 4 2012 5:03 pm
Subject: Re: [NowJS] Updating Socket.IO

Having a similar problem and I tried updating just socket.io, But still
 this warning: "client not handshaken client should reconnect" is flooding
my log file.
Thanks for Any Ideas,

On Friday, November 11, 2011 1:38:57 PM UTC-5, Eric Zhang wrote:

> Hi stefan_n,

> You should be able to run `npm update socket.io` to update the socket.ioversion. It should reach into the dependencies to update the version of
> socket.io that nowjs uses.

> Eric

> On Fri, Nov 11, 2011 at 1:10 AM, stefa_n <> wrote:

>> Hi,
>> I get an error clientside (firebug) when the connection to the server
>> gets lost:
>> "Connection to ... interrupted while the page was loading".
>> I found a hint in the Socket.IO mailing list that this is due to an
>> error that
>> should be solved in the latest version of Socket.IO.

>> As Socket.IO is a part of NowJS and not installed on its own: Is
>> there a way to update it myself or do I have to wait for a new version
>> of NowJS?

>> By the way: I get this warning:
>> "client not handshaken client should reconnect"
>> in 0.5.9 too if XHR-polling is the transport. As Scott mentioned this
>> is not
>> caused by Node 0.6. I guess this has to be solved by Socket.IO.

> --
> Co-Founder @ Flotype, makers of NowJS

On Friday, November 11, 2011 1:38:57 PM UTC-5, Eric Zhang wrote:

> Hi stefan_n,

> You should be able to run `npm update socket.io` to update the socket.ioversion. It should reach into the dependencies to update the version of
> socket.io that nowjs uses.

> Eric

> On Fri, Nov 11, 2011 at 1:10 AM, stefa_n <> wrote:

>> Hi,
>> I get an error clientside (firebug) when the connection to the server
>> gets lost:
>> "Connection to ... interrupted while the page was loading".
>> I found a hint in the Socket.IO mailing list that this is due to an
>> error that
>> should be solved in the latest version of Socket.IO.

>> As Socket.IO is a part of NowJS and not installed on its own: Is
>> there a way to update it myself or do I have to wait for a new version
>> of NowJS?

>> By the way: I get this warning:
>> "client not handshaken client should reconnect"
>> in 0.5.9 too if XHR-polling is the transport. As Scott mentioned this
>> is not
>> caused by Node 0.6. I guess this has to be solved by Socket.IO.

> --
> Co-Founder @ Flotype, makers of NowJS

On Friday, November 11, 2011 1:38:57 PM UTC-5, Eric Zhang wrote:

> Hi stefan_n,

> You should be able to run `npm update socket.io` to update the socket.ioversion. It should reach into the dependencies to update the version of
> socket.io that nowjs uses.

> Eric

> On Fri, Nov 11, 2011 at 1:10 AM, stefa_n <> wrote:

>> Hi,
>> I get an error clientside (firebug) when the connection to the server
>> gets lost:
>> "Connection to ... interrupted while the page was loading".
>> I found a hint in the Socket.IO mailing list that this is due to an
>> error that
>> should be solved in the latest version of Socket.IO.

>> As Socket.IO is a part of NowJS and not installed on its own: Is
>> there a way to update it myself or do I have to wait for a new version
>> of NowJS?

>> By the way: I get this warning:
>> "client not handshaken client should reconnect"
>> in 0.5.9 too if XHR-polling is the transport. As Scott mentioned this
>> is not
>> caused by Node 0.6. I guess this has to be solved by Socket.IO.

> --
> Co-Founder @ Flotype, makers of NowJS


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.