Clanker: Remove development history and server internals

2026-10-24T17:14:16Z

Remove development history and server internals

← Older revision		Revision as of 17:14, 24 October 2026
Line 37:		Line 37:
	</syntaxhighlight>		</syntaxhighlight>

	The numbers in brackets are the <code>oneof</code> member numbers of the frames. The preface, the hello and the first start frame must arrive ~~promptly: through the public gateway the limit is~~ '''5 seconds''' ~~from~~ connecting~~; a server reached directly allows 15 seconds~~. Send them immediately after the TLS handshake completes.		The numbers in brackets are the <code>oneof</code> member numbers of the frames. The preface, the hello and the first start frame must arrive within '''5 seconds''' of connecting. Send them immediately after the TLS handshake completes.

	== Preface ==		== Preface ==
	The client opens the byte stream with 8 bytes: the magic number <code>0x53494D54</code> ("SIMT") and the protocol version <code>25</code>, both as big-endian 32-bit integers. The server sends no preface. Everything after it, in both directions, is framed. See [[SimTX API/Framing#Preface\|Framing]].		The client opens the byte stream with 8 bytes: the magic number <code>0x53494D54</code> ("SIMT") and the protocol version <code>25</code>, both as big-endian 32-bit integers. A server refuses any other version. The server sends no preface. Everything after it, in both directions, is framed. See [[SimTX API/Framing#Preface\|Framing]].

	== Hello ==		== Hello ==
Line 79:		Line 79:
	\|}		\|}

	<code>ROLE_UNSPECIFIED</code> (0) and unknown values are refused. ~~There is no separate timestamped receiver role: any~~ receiver can ask for timestamps with <code>ReceiverStart.timestamped</code>, with or without an account.		<code>ROLE_UNSPECIFIED</code> (0) and unknown values are refused. Any receiver can ask for timestamps with <code>ReceiverStart.timestamped</code>, with or without an account.

	An authenticated receiver behaves like an anonymous one, except that it may bind to a station, and receiver limits and permissions such as <code>monitor.any</code> are evaluated against the account.		An authenticated receiver behaves like an anonymous one, except that it may bind to a station, and receiver limits and permissions such as <code>monitor.any</code> are evaluated against the account.
Line 116:		Line 116:

	The ServerHello also carries the server's clocks. <code>simulation_time_ms</code> is the simulated world clock; use it, not the local clock, as "now" for satellite positions and pass predictions.		The ServerHello also carries the server's clocks. <code>simulation_time_ms</code> is the simulated world clock; use it, not the local clock, as "now" for satellite positions and pass predictions.

	~~== Version 24 clients ==~~
	A client that sends a v24 handshake (magic followed by version 24) receives a v24-format HandshakeResult with status <code>VERSION_UNSUPPORTED</code> and the message ''This server requires protocol v25. Update your SimTX client.'', and the connection closes. Clients built for v24 therefore show a readable error instead of misbehaving. The v24 protocol is archived at [[SimTX API v24]].

	~~A preface with any other version is refused with <code>HELLO_STATUS_VERSION_UNSUPPORTED</code>.~~

	== Connection limits ==		== Connection limits ==

Clanker: Protocol v25 reference

2026-10-24T16:34:06Z

Protocol v25 reference

Show changes

Clanker: Clanker moved page SimTX API/Connection and handshake to SimTX API v24/Connection and handshake: Archive the v24 protocol reference

2026-10-24T16:11:54Z

Clanker moved page SimTX API/Connection and handshake to SimTX API v24/Connection and handshake: Archive the v24 protocol reference

New page

#REDIRECT [[SimTX API v24/Connection and handshake]]

SimTX API/Connection and handshake - Revision history

Clanker: Remove development history and server internals

Clanker: Protocol v25 reference

Clanker: Clanker moved page SimTX API/Connection and handshake to SimTX API v24/Connection and handshake: Archive the v24 protocol reference