Message types
The five wire namespaces, and every message in them.
Every message name says what kind of message it is. There are five kinds and nothing outside them — the full rule is in 03 §1.2.
session.#
Establishing and maintaining the connection itself.
| type | what it is |
|---|---|
session.denied | — |
session.describe | — |
session.going_away | MsgGoingAway -- the engine is closing on purpose and says when to come back. Without it a planned restart is indistinguishable from a crash, and every device applies crash backoff to a scheduled outage. |
session.heartbeat | — |
session.hello | — |
session.manifest | — |
record.#
What happened, or what is the case.
| type | what it is |
|---|---|
record.course | — |
record.scorecard | — |
record.shot | — |
record.state | — |
record.swing_detected | Shot correlation (06 section 10). The engine opens a pending context on the first evidence of a swing and tells the bay; devices that cannot contribute say so rather than letting the window run out. |
request.#
Asking a participant to do something — and the answer to it.
| type | what it is |
|---|---|
request.add_player | — |
request.apply_rules | — |
request.apply_rules_ack | — |
request.end_round | — |
request.remove_player | — |
request.scorecard | Requests: the engine asking a participant to change or produce something, rather than to record it. One namespace, because the complete list of things a bay can be asked is one thing a vendor should be able to read (03 section 1.1), and who may ask is the request table in the bundle rather than anyt |
request.shot_decline | — |
request.shot_extend | — |
notice.#
Addressed to a person, not to software.
| type | what it is |
|---|---|
notice.post | — |
notice.response | — |
notice.round_ending | — |
update.#
The bulk path, deliberately separate from the live path.
| type | what it is |
|---|---|
update.begin | — |
update.data | — |
update.end | — |
update.fetch | — |
update.refused | — |
Simulated Golf Association · SGA-OIS · generated from the specification sources