ReceiveWebSocket (Socket function) - Revision history

Tom: /* Usage notes */

2019-08-19T16:27:25Z

Usage notes

← Older revision		Revision as of 16:27, 19 August 2019
Line 37:		Line 37:
	==Usage notes==		==Usage notes==
	Received data may be masked by the sender. Masked data is always unmasked using the sender's masking key before it is returned to the application.		Received data may be masked by the sender. Masked data is always unmasked using the sender's masking key before it is returned to the application.

			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==

Tom: /* Examples */

2019-08-19T16:24:55Z

Examples

@@ Line 39: / Line 39: @@
 ==Examples==
 ==See also==
 {{Template:Socket:ReceiveWebSocket footer}}

Tom: /* Syntax terms */

2019-08-13T17:25:10Z

Syntax terms

← Older revision		Revision as of 17:25, 13 August 2019
Line 12:		Line 12:
	<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.</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 EBCDIC with the translate table in effect for the port.</td></tr>
	<tr><th>2</th>		<tr><th>2</th>
	<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>

Tom: /* Usage notes */

2019-08-13T17:20:13Z

Usage notes

← Older revision		Revision as of 17:20, 13 August 2019
Line 36:		Line 36:

	==Usage notes==		==Usage notes==
	Received data may be masked by the sender. Masked data is always unmasked using the ~~senders~~ masking key before it is returned to the application.		Received data may be masked by the sender. Masked data is always unmasked using the sender's masking key before it is returned to the application.

	==Examples==		==Examples==
	==See also==		==See also==
	{{Template:Socket:ReceiveWebSocket footer}}		{{Template:Socket:ReceiveWebSocket footer}}

Tom: /* Usage notes */

2019-08-13T17:19:54Z

Usage notes

← Older revision		Revision as of 17:19, 13 August 2019
Line 36:		Line 36:

	==Usage notes==		==Usage notes==
			Received data may be masked by the sender. Masked data is always unmasked using the senders masking key before it is returned to the application.

	==Examples==		==Examples==
	==See also==		==See also==
	{{Template:Socket:ReceiveWebSocket footer}}		{{Template:Socket:ReceiveWebSocket footer}}

Tom: /* Syntax terms */

2019-08-13T17:17:33Z

Syntax terms

← Older revision		Revision as of 17:17, 13 August 2019
Line 7:		Line 7:
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th>%opCode</th>		<tr><th>%opCode</th>
	<td>~~number is an~~ op code indicating the type of web socket frame. Numbers 0-7 are non-control frames. Numbers 8-15 are control frames~~. Control frames are always sent immediately and cannot be fragmented. Specifying a reserved code will cause immediate request cancellation~~.		<td>op code is a number indicating the type of web socket frame received. Numbers 0-7 are non-control frames. Numbers 8-15 are control frames.
	<table>		<table>
	<tr><th>0</th>		<tr><th>0</th>
Line 18:		Line 18:
	<td>Reserved for future use.</td></tr>		<td>Reserved for future use.</td></tr>
	<tr><th>8</th>		<tr><th>8</th>
	<td>Connection close frame.</td></tr>		<td>Connection close frame. A close frame should be sent in response.</td></tr>
	<tr><th>9</th>		<tr><th>9</th>
	<td>Ping. The receiver should respond with a Pong frame, unless a close frame has been received.</td></tr>		<td>Ping. The receiver should respond with a Pong frame, unless a close frame has been received.</td></tr>

Tom: /* Syntax terms */

2019-08-13T17:14:25Z

Syntax terms

@@ Line 6: / Line 6: @@
 ===Syntax terms===
 <table class="syntaxTable">
-<tr><th>%opCode</th><td>number</td></tr>
+<tr><th>%opCode</th>
 <tr><th>socket</th>
 <td>Socket object</td></tr>
@@ Line 12: / Line 34: @@
 <td>string</td></tr>
 </table>
 ==Usage notes==
 ==Examples==
 ==See also==
 {{Template:Socket:ReceiveWebSocket footer}}

DmeWiccan: Automatically generated page update

2019-03-26T02:41:22Z

Automatically generated page update

New page

{{Template:Socket:ReceiveWebSocket subtitle}}

This page is [[under construction]].
==Syntax==
{{Template:Socket:ReceiveWebSocket syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%opCode</th><td>number</td></tr>
<tr><th>socket</th>
<td>Socket object</td></tr>
<tr><th>string</th>
<td>string</td></tr>
</table>
==Usage notes==
==Examples==
==See also==
{{Template:Socket:ReceiveWebSocket footer}}