srt_protocol/options/mod.rs
1mod address;
2mod bandwidth;
3mod bind;
4mod caller;
5mod connect;
6mod encryption;
7mod error;
8mod listener;
9mod receiver;
10mod rendezvous;
11mod sender;
12mod session;
13mod socket;
14mod srt_version;
15mod stream_id;
16mod units;
17mod uri;
18mod validation;
19
20pub use address::*;
21pub use bandwidth::*;
22pub use bind::*;
23pub use caller::*;
24pub use connect::*;
25pub use encryption::*;
26pub use error::*;
27pub use listener::*;
28pub use receiver::*;
29pub use rendezvous::*;
30pub use sender::*;
31pub use session::*;
32pub use socket::*;
33pub use srt_version::*;
34pub use stream_id::*;
35pub use units::*;
36pub use uri::url_parse;
37pub use validation::*;
38
39// see https://github.com/Haivision/srt/blob/master/docs/API/API-socket-options.md
40
41// SRTO_PACKETFILTER - FEC not supported... yet
42
43// TODO: look over these options, they could be useful for statistics
44//
45// SRTO_EVENT - events? not a configuration option
46// SRTO_PEERVERSION - read only, could be helpful as a statistic
47// SRTO_RCVDATA - read only, could be helpful as a statistic
48// SRTO_RCVKMSTATE - read only, could be helpful as a statistic?
49// SRTO_RENDEZVOUS - read only, maybe useful as as a read only setting?
50// SRTO_SNDDATA - read only, but useful as a statistic
51// Size of the unacknowledged data in send buffer.
52// SRTO_SNDKMSTATEE - read only, maybe as a statistic?
53// SRTO_VERSION - maybe useful either as a setting or statistic?
54
55// NOTE: will not implement these configuration options
56//
57// SRTO_IPTOS - socket specific
58// SRTO_IPTTL - socket specific
59// SRTO_IPV6ONLY - socket specific
60// SRTO_LINGER - socket specific
61// SRTO_TRANSTYPE - socket specific
62// SRTO_BINDTODEVICE - socket only
63// SRTO_REUSEADDR - socket specific
64// SRTO_STATE - socket specific
65// SRTO_RCVSYN - not even relevant for tokio
66// SRTO_RCVTIMEO - not even relevant for tokio
67// SRTO_SNDSYN - not even relevant for tokio
68// SRTO_SNDTIMEO - not even relevant for tokio
69// SRTO_KMSTATE - legacy, not supporting
70// SRTO_ISN - only good for development scenarios
71// SRTO_UDP_SNDBUF - not really relevant for tokio is it?
72// SRTO_UDP_RCVBUF - not really relevant for tokio, is it?
73// SRTO_SENDER - always duplex
74// SRTO_MESSAGEAPI - only "live" is supported
75// SRTO_CONGESTION - only "live" is supported
76// SRTO_ENFORCEDENCRYPTION - awkward/arcane - is this actually useful?