Skip to content

Any plan for handling "ka" (keep-alive) and ping-pong checks? #200

Closed
@sneko

Description

@sneko

Hi @leszekhanusz ,

I'm wondering if there is any plan to support the keep-alive message? It comes from the server to make sure the connection is still alive, and if the client receives no KA within a specific timeout defined, it behaves as the connection was lost.

When seeing:

"""Wait for the connection_ack message. Keep alive messages are ignored

and:
# KeepAlive message

I understand that's not implemented, but just wondering if it's in the pipe.

Also, in the same kind of standards, Keep-Alive makes sure the client will react in case of lost connection, but on it's end the server won't know if the connection was lost (router shut down for example, or loss of connectivity, that are not proper terminations). This is usually handled for websockets by an end-to-end "ping-pong" protocol between the client and the server:

  • The server sends a "ping" every X interval
  • The client has to reply "pong" within a timeout defined otherwise the server considers the connection as lost (which help freeing memory and doing specific stuff like updating client status in the database...)

Is it also something on your plan? It would definitely help.

Thank you,

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions