Online Amateur Radio Community Wiki

User Tools

Site Tools

Trace:
packet:white-papers:pwp-0222

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
packet:white-papers:pwp-0222 [2026/04/29 21:25] – m0ltepacket:white-papers:pwp-0222 [2026/04/29 21:38] (current) – [10. References] m0lte
Line 817: Line 817:
  
 - Client sends OPEN message, specifying the radio port, plus source and destination calls (including digipeaters if required). - Client sends OPEN message, specifying the radio port, plus source and destination calls (including digipeaters if required).
-- Server immediately replies with OPENREPLY, containing a socket "handle" for all subsequent operations on the socket.+- Server immediately replies with OPEN_REPLY, containing a socket "handle" for all subsequent operations on the socket.
 - If the connection succeeds, the server asynchronously sends a STATUS message indicating "connected". If the connection fails, the status message contains "disconnected" instead. - If the connection succeeds, the server asynchronously sends a STATUS message indicating "connected". If the connection fails, the status message contains "disconnected" instead.
 - The client sends data to the connection using SEND messages, the payload of which is JSON-escaped so it can handle full binary. - The client sends data to the connection using SEND messages, the payload of which is JSON-escaped so it can handle full binary.
-- SEND messages are acknowledged using SENDREPLY.+- SEND messages are acknowledged using SEND_REPLY.
 - If the client sends too much data for the AX25 link to handle, the server sends a STATUS message with the BUSY flag set. When clear to send again, the server sends a STATUS message with the BUSY flag unset. - If the client sends too much data for the AX25 link to handle, the server sends a STATUS message with the BUSY flag set. When clear to send again, the server sends a STATUS message with the BUSY flag unset.
 - Data received from the downlink is sent to the client in RECV messages, with the payload JSON-escaped. - Data received from the downlink is sent to the client in RECV messages, with the payload JSON-escaped.
 - If the downlink initiates a disconnect, the server sends a STATUS message to the client with the CONNECTED flag set to "false". The client must now issue a CLOSE to dispose of the socket. - If the downlink initiates a disconnect, the server sends a STATUS message to the client with the CONNECTED flag set to "false". The client must now issue a CLOSE to dispose of the socket.
-- Alternatively, if the client wishes to terminate the connection it issues a CLOSE request, and the server responds with a CLOSEREPLY.+- Alternatively, if the client wishes to terminate the connection it issues a CLOSE request, and the server responds with a CLOSE_REPLY.
  
 ==== 6.2. Incoming Connection ==== ==== 6.2. Incoming Connection ====
Line 830: Line 830:
  
 - The client sends an OPEN message, specifying the XRouter PORT number and the local callsign. This creates a "listener" socket. - The client sends an OPEN message, specifying the XRouter PORT number and the local callsign. This creates a "listener" socket.
-- The server responds with an OPENREPLY message containing the socket handle (or an error code).+- The server responds with an OPEN_REPLY message containing the socket handle (or an error code).
 - If someone connects to the callsign associated with the socket, the server immediately sends an ACCEPT message to the client, containing the socket handle and the callsign of the connectee. - If someone connects to the callsign associated with the socket, the server immediately sends an ACCEPT message to the client, containing the socket handle and the callsign of the connectee.
 - The remainder of the connection proceeds as in step 4 of the Outgoing Connection flow above. - The remainder of the connection proceeds as in step 4 of the Outgoing Connection flow above.
Line 854: Line 854:
  
 ===== 10. References ===== ===== 10. References =====
-- Dowie P., "Remote Host Protocol", PWP 144, December 2004. +[1] Dowie P., "Remote Host Protocol", PWP 144, December 2004.\\  
-- Dowie P., "NET/ROM Data Multiplexing", PWP 109, July 2001.+[2] Dowie P., "NET/ROM Data Multiplexing", PWP 109, July 2001.
  
 ---- ----
 //PWP222 Remote Host Protocol Version 2 — June 2023// //PWP222 Remote Host Protocol Version 2 — June 2023//
packet/white-papers/pwp-0222.1777497943.txt.gz · Last modified: by m0lte