You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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...
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
The text was updated successfully, but these errors were encountered: