PowerBuilder

Send a WebSocket Ping Control Frame

See more WebSocket Examples

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.

PowerBuilder

integer li_rc
integer li_Success
oleobject loo_Ws
oleobject loo_Rest
string ls_ResponseBodyIgnored
integer li_FinalFrame
integer li_ReceivedFinalFrame
string ls_ReceivedMsg

li_Success = 0

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

loo_Ws = create oleobject
li_rc = loo_Ws.ConnectToNewObject("Chilkat.WebSocket")
if li_rc < 0 then
    destroy loo_Ws
    MessageBox("Error","Connecting to COM object failed")
    return
end if

// 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.
loo_Ws.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.

loo_Rest = create oleobject
li_rc = loo_Rest.ConnectToNewObject("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.
li_Success = loo_Rest.Connect("websockets.chilkat.io",80,0,0)
loo_Ws.UseConnection(loo_Rest)
loo_Ws.AddClientHeaders()
ls_ResponseBodyIgnored = loo_Rest.FullRequestNoBody("GET","/wsChilkatEcho.ashx")
li_Success = loo_Ws.ValidateServerHandshake()
if li_Success <> 1 then
    Write-Debug loo_Ws.LastErrorText
    destroy loo_Ws
    destroy loo_Rest
    return
end if

// 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.
li_FinalFrame = 0
li_Success = loo_Ws.SendFrame("This is the 1st frame~r~n",li_FinalFrame)
if li_Success <> 1 then
    Write-Debug loo_Ws.LastErrorText
    destroy loo_Ws
    destroy loo_Rest
    return
end if

// Let's send a Ping frame here...
li_Success = loo_Ws.SendPing("This is a ping")
if li_Success <> 1 then
    Write-Debug loo_Ws.LastErrorText
    destroy loo_Ws
    destroy loo_Rest
    return
end if

// Send the 2nd frame in the message.
li_Success = loo_Ws.SendFrame("This is the 2nd frame~r~n",li_FinalFrame)
if li_Success <> 1 then
    Write-Debug loo_Ws.LastErrorText
    destroy loo_Ws
    destroy loo_Rest
    return
end if

// Send the 3rd and final frame in the message.
li_FinalFrame = 1
li_Success = loo_Ws.SendFrame("This is the 3rd and final frame~r~n",li_FinalFrame)
if li_Success <> 1 then
    Write-Debug loo_Ws.LastErrorText
    destroy loo_Ws
    destroy loo_Rest
    return
end if

// 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.
li_ReceivedFinalFrame = 0
do while li_ReceivedFinalFrame = 0

    li_Success = loo_Ws.ReadFrame()
    if li_Success <> 1 then
        Write-Debug "Failed to receive a frame"
        Write-Debug "ReadFrame fail reason = " + string(loo_Ws.ReadFrameFailReason)
        Write-Debug loo_Ws.LastErrorText
        destroy loo_Ws
        destroy loo_Rest
        return
    end if

    li_ReceivedFinalFrame = loo_Ws.FinalFrame

    // Show the opcode and final frame bit for the frame just received:
    Write-Debug "Frame opcode: " + loo_Ws.FrameOpcode
    Write-Debug "Final frame: " + string(li_ReceivedFinalFrame)
    Write-Debug "--"
loop

// Return the message accumulated in the above calls to ReadFrame.
ls_ReceivedMsg = loo_Ws.GetFrameData()
Write-Debug "Received: " + ls_ReceivedMsg

// Close the websocket connection.
li_Success = loo_Ws.SendClose(1,1000,"Closing this websocket.")
if li_Success <> 1 then
    Write-Debug loo_Ws.LastErrorText
    destroy loo_Ws
    destroy loo_Rest
    return
end if

// Read the Close response.
li_Success = loo_Ws.ReadFrame()
if li_Success <> 1 then
    Write-Debug "ReadFrame fail reason = " + string(loo_Ws.ReadFrameFailReason)
    Write-Debug loo_Ws.LastErrorText
    destroy loo_Ws
    destroy loo_Rest
    return
end if

// Should receive the "Close" opcode.
Write-Debug "Received opcode: " + loo_Ws.FrameOpcode
// Should be the same status code we sent (1000)
Write-Debug "Received close status code: " + string(loo_Ws.CloseStatusCode)
// The server may echo the close reason.  If not, this will be empty.
Write-Debug "Echoed close reason: " + loo_Ws.CloseReason

Write-Debug "Success."


destroy loo_Ws
destroy loo_Rest