Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HeartBeat explanation #6

Open
pmarques opened this issue Aug 2, 2011 · 2 comments
Open

HeartBeat explanation #6

pmarques opened this issue Aug 2, 2011 · 2 comments

Comments

@pmarques
Copy link

pmarques commented Aug 2, 2011

Hi,

Can you clarify the workflow of heartbeat?
I'm implementing the Socket.IO protocol, but reading this spec and "sniff" some socket.IO packages of a JS implementation make me a litle confused.
This spec tells that "it's up to the client to decide the padding", but has far as I can see this is done by the server, the client only reply to the Server HeartBeats (instantly). In other words, i didn't realize if the initiative to send the heartbeat comes from server or the client.
So, If is the server who has the initiative, maybe this spec is a bit unclear?

Regardes,
Patrick

@purefan
Copy link

purefan commented Oct 14, 2011

In general Im finding the documentation surrounding socket.io very lacking... it does work pretty well but learning about it is turning into a quest in its own...

@vongosling
Copy link

from my experience,heartbeat initiative come from sever,the client may modify this number according itself case!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants