1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
use crateprotocol;
use Cow;
/// The MSEX layer provides a standard, single, header used at the start of all MSEX packets.
///
/// The `content_type` field identifies the specific MSEX message type (e.g. "GETh" for Get Element
/// Thumbnail, etc). If an implementation receives a message with an unrecognised cookie it must
/// silently discard the message and not treat this as an error condiion. This is to allow the
/// specification to continue to evolve over time.
/// Layout of MSEX messages.
/// ## MSEX / CINF - Client Information message
///
/// The Client Information message advises the media server of which versions of MSEX are supported
/// by the client. This message is mandatory and must be sent by the client to the media server
/// immediately after establishing a connection. The media server will examine the list of
/// supported versions and establish the Highest Common MSEX version defined above.
///
/// **Note**: The format of this message up to FutureMessageData cannot be changed in future
/// versions of MSEX, since the client does not y et know which versions te media server will
/// understand. Future versions can be defined however, but they must preserve the format of the
/// previous version and only insert new fields immediately before the FutureMessageData field.