Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      PingMessage should be PongMessage. I will fix it in next version.

      What we agreed in the expert group way back was that we should have api to send pings. But since the websocket protocol requires implementations to respond to a ping with a pong with the same binary data in it, we agreed we didn't want developer to have to program sending a pong in response to a ping. So they can send pings and listen for pongs, but they don't need to listen for pings. They are able to send an unsolicited Pong if they want to (the protocol allows this).

        Activity

        Hide
        dannycoward added a comment -

        This issue has been updated in the workspace, and is clarified in the upcoming v010 release.

        Show
        dannycoward added a comment - This issue has been updated in the workspace, and is clarified in the upcoming v010 release.

          People

          • Assignee:
            dannycoward
            Reporter:
            dannycoward
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: