moq_transport

Module message

Source
Expand description

Low-level message sent over the wire, as defined in the specification.

TODO Update this All of these messages are sent over a bidirectional QUIC stream. This introduces some head-of-line blocking but preserves ordering. The only exception are OBJECT “messages”, which are sent over dedicated QUIC streams.

Messages sent by the publisher:

Messages sent by the subscriber:

Example flow:

 -> ANNOUNCE        namespace="foo"
 <- ANNOUNCE_OK     namespace="foo"
 <- SUBSCRIBE       id=0 namespace="foo" name="bar"
 -> SUBSCRIBE_OK    id=0
 -> OBJECT          id=0 sequence=69 priority=4 expires=30
 -> OBJECT          id=0 sequence=70 priority=4 expires=30
 -> OBJECT          id=0 sequence=70 priority=4 expires=30
 <- SUBSCRIBE_STOP  id=0
 -> SUBSCRIBE_RESET id=0 code=206 reason="closed by peer"

Structs§

Enums§

  • Filter Types https://www.ietf.org/archive/id/draft-ietf-moq-transport-04.html#name-filter-types
  • Group Order https://www.ietf.org/archive/id/draft-ietf-moq-transport-05.html#section-6.4.2-4.6.1 https://www.ietf.org/archive/id/draft-ietf-moq-transport-05.html#priorities
  • All supported message types.
  • Signal where the subscription should begin, relative to the current cache.
  • Track Status Codes https://www.ietf.org/archive/id/draft-ietf-moq-transport-04.html#name-track_status