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
Socket.IO
Home
+ new post
About this group
Join this group
socket.io set heartbeat timeout
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
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
 
Morgan Fromentin  
View profile  
 More options Oct 31 2012, 5:33 am
From: Morgan Fromentin <morgan.fromen...@gmail.com>
Date: Wed, 31 Oct 2012 02:33:19 -0700 (PDT)
Local: Wed, Oct 31 2012 5:33 am
Subject: socket.io set heartbeat timeout
Print | Individual message | Show original | Report this message | Find messages by this author

Hello everybody,

I'm working on a a google chrome extension using socket.io.
Despite problems regarding chrome extension itself, I have a problem with a
basic example using socket.io

I always get that:

debug - setting request GET /socket.io/1/websocket/2Ioi1TBLwhjNp3M8kCVF
   debug - set heartbeat interval for client 2Ioi1TBLwhjNp3M8kCVF
   debug - client authorized for
   debug - websocket writing 1::
   debug - websocket writing 5:::{"name":"news","args":[{"hello":"world"}]}
   debug - emitting heartbeat for client 2Ioi1TBLwhjNp3M8kCVF
   debug - websocket writing 2::
   debug - set heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - got heartbeat packet
   debug - cleared heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - set heartbeat interval for client 2Ioi1TBLwhjNp3M8kCVF
   debug - emitting heartbeat for client 2Ioi1TBLwhjNp3M8kCVF
   debug - websocket writing 2::
   debug - set heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - got heartbeat packet
   debug - cleared heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - set heartbeat interval for client 2Ioi1TBLwhjNp3M8kCVF
   debug - emitting heartbeat for client 2Ioi1TBLwhjNp3M8kCVF
   debug - websocket writing 2::
   debug - set heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - got heartbeat packet
   debug - cleared heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - set heartbeat interval for client 2Ioi1TBLwhjNp3M8kCVF
   debug - emitting heartbeat for client 2Ioi1TBLwhjNp3M8kCVF
   debug - websocket writing 2::
   debug - set heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - got heartbeat packet
   debug - cleared heartbeat timeout for client 2Ioi1TBLwhjNp3M8kCVF
   debug - set heartbeat interval for client 2Ioi1TBLwhjNp3M8kCVF

whatever the browser is.
I was previously in https, I changed back to http, problem remains the same.
Nodejs is running in a amazon ec2 instance, could it simply be a latence
problem with the instance ?

Thanks in advance.


 
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.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google