|<< Back to previous view|
[WEBSOCKET_SPEC-65] PingMessage should be PongMessage Created: 05/Dec/12 Updated: 08/Dec/12 Resolved: 08/Dec/12
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
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).
|Comment by dannycoward [ 08/Dec/12 12:21 AM ]|
This issue has been updated in the workspace, and is clarified in the upcoming v010 release.