(Visual FoxPro) Send a WebSocket Ping Control Frame

Ping and Pong messages are the heartbeat of websockets. See Pings and Pongs

"At any point after the handshake, either the client or the server can choose to send a ping to the other party. When the ping is received, the recipient must send back a pong as soon as possible. You can use this to make sure that the client is still connected, for example. A ping or pong is just a regular frame, but it's a control frame. Pings have an opcode of 0x9, and pongs have an opcode of 0xA. When you get a ping, send back a pong with the exact same Payload Data as the ping (for pings and pongs, the max payload length is 125). You might also get a pong without ever sending a ping; ignore this if it happens."

This example demonstrates how to send a Ping in the midst of sending a message.

Note: The websockets.chilkat.io server imposes the following limitations:
Messages must be 16K or less, and each connection is limited to a max of 16 echoed messages.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

LOCAL loWs
LOCAL loRest
LOCAL lnSuccess
LOCAL lcResponseBodyIgnored
LOCAL lnFinalFrame
LOCAL lnReceivedFinalFrame
LOCAL lcReceivedMsg

* This example requires the Chilkat API to have been previously unlocked.
* See Global Unlock Sample for sample code.

* For versions of Chilkat < 10.0.0, use CreateObject('Chilkat_9_5_0.WebSocket')
loWs = CreateObject('Chilkat.WebSocket')

* The PongAutoConsume property is 1 by default.  This means that any Pong frames that are received 
* will automatically be consumed, and the ReadFrame method will continue reading the next incoming frame before it returns.
loWs.PongAutoConsume = 1

* For brevity, this example does not check for errors when etablishing the WebSocket connection.
* See Establish WebSocket Connection for more complete sample code for making the connection.

* For versions of Chilkat < 10.0.0, use CreateObject('Chilkat_9_5_0.Rest')
loRest = CreateObject('Chilkat.Rest')
* Connect to websockets.chilkat.io
* IMPORTANT: websockets.chilkat.io accepts frames of up to 16K in size and echoes them back.
* IMPORTANT: The websockets.chilkat.io server imposes the following limitations: 
* ---------- Messages must be 16K or less, and each connection is limited to a max of 16 echoed messages.
lnSuccess = loRest.Connect("websockets.chilkat.io",80,0,0)
loWs.UseConnection(loRest)
loWs.AddClientHeaders()
lcResponseBodyIgnored = loRest.FullRequestNoBody("GET","/wsChilkatEcho.ashx")
lnSuccess = loWs.ValidateServerHandshake()
IF (lnSuccess <> 1) THEN
    ? loWs.LastErrorText
    RELEASE loWs
    RELEASE loRest
    CANCEL
ENDIF

* This example sends a multi-frame message to the Chilkat echo server, and reads the response.
* In the midst of sending the message, we'll send a Ping control frame.  The server should respond with a Pong frame,
* and we'll automatically consume it.

* Send the 1st frame in the message.
lnFinalFrame = 0
lnSuccess = loWs.SendFrame("This is the 1st frame" + CHR(13) + CHR(10),lnFinalFrame)
IF (lnSuccess <> 1) THEN
    ? loWs.LastErrorText
    RELEASE loWs
    RELEASE loRest
    CANCEL
ENDIF

* Let's send a Ping frame here...
lnSuccess = loWs.SendPing("This is a ping")
IF (lnSuccess <> 1) THEN
    ? loWs.LastErrorText
    RELEASE loWs
    RELEASE loRest
    CANCEL
ENDIF

* Send the 2nd frame in the message.
lnSuccess = loWs.SendFrame("This is the 2nd frame" + CHR(13) + CHR(10),lnFinalFrame)
IF (lnSuccess <> 1) THEN
    ? loWs.LastErrorText
    RELEASE loWs
    RELEASE loRest
    CANCEL
ENDIF

* Send the 3rd and final frame in the message.
lnFinalFrame = 1
lnSuccess = loWs.SendFrame("This is the 3rd and final frame" + CHR(13) + CHR(10),lnFinalFrame)
IF (lnSuccess <> 1) THEN
    ? loWs.LastErrorText
    RELEASE loWs
    RELEASE loRest
    CANCEL
ENDIF

* Read an incoming frames until we receive the final frame.
* Note: It may be that the echo server (websockets.chilkat.io) responds with 
* the full message in a single final frame.
* 
* The Pong response will be consumed automatically because the PongAutoConsume property is 1.
* Therefore, we don't need to worry about handling an incoming Pong.
lnReceivedFinalFrame = 0
DO WHILE lnReceivedFinalFrame = 0

    lnSuccess = loWs.ReadFrame()
    IF (lnSuccess <> 1) THEN
        ? "Failed to receive a frame"
        ? "ReadFrame fail reason = " + STR(loWs.ReadFrameFailReason)
        ? loWs.LastErrorText
        RELEASE loWs
        RELEASE loRest
        CANCEL
    ENDIF

    lnReceivedFinalFrame = loWs.FinalFrame

    * Show the opcode and final frame bit for the frame just received:
    ? "Frame opcode: " + loWs.FrameOpcode
    ? "Final frame: " + STR(lnReceivedFinalFrame)
    ? "--"
ENDDO

* Return the message accumulated in the above calls to ReadFrame.
lcReceivedMsg = loWs.GetFrameData()
? "Received: " + lcReceivedMsg

* Close the websocket connection.
lnSuccess = loWs.SendClose(1,1000,"Closing this websocket.")
IF (lnSuccess <> 1) THEN
    ? loWs.LastErrorText
    RELEASE loWs
    RELEASE loRest
    CANCEL
ENDIF

* Read the Close response.
lnSuccess = loWs.ReadFrame()
IF (lnSuccess <> 1) THEN
    ? "ReadFrame fail reason = " + STR(loWs.ReadFrameFailReason)
    ? loWs.LastErrorText
    RELEASE loWs
    RELEASE loRest
    CANCEL
ENDIF

* Should receive the "Close" opcode.
? "Received opcode: " + loWs.FrameOpcode
* Should be the same status code we sent (1000)
? "Received close status code: " + STR(loWs.CloseStatusCode)
* The server may echo the close reason.  If not, this will be empty.
? "Echoed close reason: " + loWs.CloseReason

? "Success."

RELEASE loWs
RELEASE loRest