Skip to content

HeartBeat explanation #6

@pmarques

Description

@pmarques

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions