SendWebSocket (Socket function) - Revision history

Tom: /* Usage notes */

2024-07-29T19:53:08Z

Usage notes

← Older revision		Revision as of 19:53, 29 July 2024
Line 36:		Line 36:
	</table>		</table>

	~~==Usage notes==~~		Sending a control frame always forces a flush of the TCP output buffer. A close or a ping are the only valid control frames.

	==Examples==		==Examples==
	The following example sends a text message to the WebSocket client.		The following example sends a text message to the WebSocket client.

2019-08-19T16:21:24Z

Examples

← Older revision		Revision as of 16:21, 19 August 2019
Line 38:		Line 38:
	==Usage notes==		==Usage notes==
	==Examples==		==Examples==
	The following example ~~send~~ a text message to the WebSocket ~~clientg~~.		The following example sends a text message to the WebSocket client.
	<p class="code">...		<p class="code">...

2019-08-19T16:18:51Z

Examples

← Older revision		Revision as of 16:18, 19 August 2019
Line 40:		Line 40:
	The following example send a text message to the WebSocket clientg.		The following example send a text message to the WebSocket clientg.
	<p class="code">...		<p class="code">...
	~~...~~

	%sock = WebSocket		%sock = WebSocket

2019-08-19T16:18:33Z

Examples

← Older revision		Revision as of 16:18, 19 August 2019
Line 38:		Line 38:
	==Usage notes==		==Usage notes==
	==Examples==		==Examples==
			The following example send a text message to the WebSocket clientg.
			<p class="code">...
	...		...

Line 53:		Line 55:

	...		...
			</p>

	==See also==		==See also==
	{{Template:Socket:SendWebSocket footer}}		{{Template:Socket:SendWebSocket footer}}

2019-08-19T16:15:40Z

Examples

@@ Line 38: / Line 38: @@
 ==Usage notes==
 ==Examples==
 ==See also==
 {{Template:Socket:SendWebSocket footer}}

2019-08-19T16:00:25Z

← Older revision		Revision as of 16:00, 19 August 2019
Line 6:		Line 6:
	===Syntax terms===		===Syntax terms===
	<table class="syntaxTable">		<table class="syntaxTable">
	~~<tr><th>%number</th><td>Always returns zero. Any error will cause request cancellation.</td></tr>~~
	<tr><th>socket</th>		<tr><th>socket</th>
	<td>Socket object</td></tr>		<td>Socket object</td></tr>

2019-08-13T17:27:50Z

Syntax terms

← Older revision		Revision as of 17:27, 13 August 2019
Line 21:		Line 21:
	<td>A binary frame. No translation is done for binary frames.</td></tr>		<td>A binary frame. No translation is done for binary frames.</td></tr>
	<tr><th>3-7</th>		<tr><th>3-7</th>
	<td>Reserved for future use.</td></tr>		<td>Reserved for future use and will cause request cancellation.</td></tr>
	<tr><th>8</th>		<tr><th>8</th>
	<td>Connection close frame.</td></tr>		<td>Connection close frame.</td></tr>
Line 29:		Line 29:
	<td>Pong. This is sent as a response to a Ping frame.</td></tr>		<td>Pong. This is sent as a response to a Ping frame.</td></tr>
	<tr><th>11-15</th>		<tr><th>11-15</th>
	<td>Reserved for future use.</td></tr>		<td>Reserved for future use and will cause request cancellation.</td></tr>
	<tr><th>128</th>		<tr><th>128</th>
	<td>This value is added to the frame op code to indicate the final fragment of a non-control message. The first fragment may also be the final fragment.</td></tr>		<td>This value is added to the frame op code to indicate the final fragment of a non-control message. The first fragment may also be the final fragment.</td></tr>

2019-08-13T17:24:30Z

Syntax terms

← Older revision		Revision as of 17:24, 13 August 2019
Line 15:		Line 15:
	<table>		<table>
	<tr><th>0</th>		<tr><th>0</th>
	<td>A continuation frame. A continuation frame is treated as text or binary based on the op code of the first frame.</td></tr>		<td>A continuation frame. A continuation frame is treated as text or binary based on the op code of the first frame. A continuation frame cannot also be the first frame.</td></tr>
	<tr><th>1</th>		<tr><th>1</th>
	<td>A text frame. Text frames are are translated to ASCII with the translate table in effect for the port.</td></tr>		<td>A text frame. Text frames are are translated to ASCII with the translate table in effect for the port.</td></tr>

2019-08-13T16:45:27Z

Syntax terms

← Older revision		Revision as of 16:45, 13 August 2019
Line 6:		Line 6:
	===Syntax terms===		===Syntax terms===
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th>%number</th><td>~~number~~</td></tr>		<tr><th>%number</th><td>Always returns zero. Any error will cause request cancellation.</td></tr>
	<tr><th>socket</th>		<tr><th>socket</th>
	<td>Socket object</td></tr>		<td>Socket object</td></tr>

2019-08-13T16:38:19Z

Syntax terms

← Older revision		Revision as of 16:38, 13 August 2019
Line 25:		Line 25:
	<td>Connection close frame.</td></tr>		<td>Connection close frame.</td></tr>
	<tr><th>9</th>		<tr><th>9</th>
	<td>Ping.</td></tr>		<td>Ping. The receiver should respond with a Pong frame, unless a close frame has been received.</td></tr>
	<tr><th>10</th>		<tr><th>10</th>
	<td>Pong.</td></tr>		<td>Pong. This is sent as a response to a Ping frame.</td></tr>
	<tr><th>11-15</th>		<tr><th>11-15</th>
	<td>Reserved for future use.</td></tr>		<td>Reserved for future use.</td></tr>
Line 33:		Line 33:
	<td>This value is added to the frame op code to indicate the final fragment of a non-control message. The first fragment may also be the final fragment.</td></tr>		<td>This value is added to the frame op code to indicate the final fragment of a non-control message. The first fragment may also be the final fragment.</td></tr>
	</table></td></tr>		</table></td></tr>
	~~</td></tr>~~
	<tr><th>boolean</th>		<tr><th>boolean</th>
	<td><var>Boolean</var> value that indicates whether to mask the data with a masking key. The default is not to mask the data. Masking is done using an internally generated masking key.</td></tr>		<td><var>Boolean</var> value that indicates whether to mask the data with a masking key. The default is not to mask the data. Masking is done using an internally generated masking key.</td></tr>