mirror of
https://github.com/mumble-voip/mumble.git
synced 2025-10-26 11:19:16 +00:00
Drop the 'unreliable' label from UDP. Delivery is not guaranteed, but delivery reliability largely depends on network context. Unreliable makes it sound more negative and error-prone than it is. We use UDP because and with the understanding that in most cases it is quite reliable, or reliable enough, rather than simply being unreliable. The point is that we use it for low-latency. Everything else is technical reasoning. Prefer short statement sentences over long comma sentences. 'an TLSv1 encrypted connection' -> 'a TLSv1 encrypted connection' Format message type name as inline code to indicate it being a "type" name. |
||
|---|---|---|
| .. | ||
| resources | ||
| establishing_connection.md | ||
| overview.md | ||
| protocol_stack_tcp.md | ||
| README.md | ||
| voice_data.md | ||
Mumble Network Protocol Documentation
The Mumble Network Protocol documentation is meant to be a reference for the Mumble VoIP 1.2.X server-client communication protocol. It reflects the state of the protocol implemented in the Mumble 1.2.8 client and might be outdated by the time you are reading this.
For up to date message type and message structure information
refer to the Mumble.proto
and MumbleUDP.proto
protobuf definition files.
This documentation is split into