oxideav-rtmp 0.0.4

Pure-Rust RTMP (ingest + push) for oxideav — server accepts publishers, client pushes to remote servers, with a pluggable key-verification hook
Documentation 
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
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

//! Pure-Rust RTMP for oxideav — ingest + push.
//!
//! This crate lets callers:
//!
//! * **Accept** an incoming publisher ([`RtmpServer`]). One TCP
//!   connection per publisher, blocking-thread-per-connection. Server
//!   drives the RTMP handshake + connect + createStream + publish
//!   handshake, then hands the consumer a [`PublishRequest`] carrying
//!   the `app`, `stream_name`, `tc_url`, and `peer_addr` so the
//!   consumer can verify the stream key / do whatever auth they want
//!   before accepting. Accepted publishers become an [`RtmpSession`]
//!   emitting audio / video / metadata packets.
//!
//! * **Push** an encoded stream out to a remote RTMP server
//!   ([`RtmpClient`]). Dial an `rtmp://host[:port]/app/stream_name`
//!   URL, run the client-side publish handshake, then call
//!   `send_video` / `send_audio` / `send_metadata` with H.264 /
//!   AAC payloads.
//!
//! The protocol pieces are reusable on their own —
//! [`amf`], [`chunk`], [`flv`], [`message`], [`handshake`] — for
//! callers who need an RTMP primitive the high-level API doesn't
//! expose yet.
//!
//! AMF support:
//!
//! * [`amf`] — AMF0 wire format (the default for RTMP command +
//!   metadata messages). Used by every commodity ingest endpoint.
//! * [`amf3`] — AMF3 wire format, the Flash Player 9+ binary
//!   serialization. RTMP can switch a channel to AMF3 via the AMF0
//!   `avmplus-object-marker` (0x11) or by using message type IDs 15
//!   (Data), 16 (Shared Object) and 17 (Command). The encoder + decoder
//!   handle all thirteen markers plus the three reference tables
//!   (strings / objects / traits).
//!
//! Out of scope for this release:
//!
//! * RTMPS (TLS). Consumers who need it can wrap our `Read + Write`
//!   with rustls. We may add an `rtmps` feature later.
//! * RTMP play (downstream subscriber / upstream pull). Only publish
//!   direction is implemented.
//! * Shared objects, RTMFP, RTMP Encrypted, and the Adobe
//!   digest-verified handshake variant.

pub mod adapter;
pub mod amf;
pub mod amf3;
pub mod chunk;
pub mod client;
pub mod error;
pub mod flv;
pub mod handshake;
pub mod message;
pub mod server;

pub use adapter::{
    audio_codec_id, audio_codec_id_for_tag, audio_fourcc_codec_id, audio_to_packet, open_rtmp,
    register, video_codec_id, video_codec_id_for_tag, video_fourcc_codec_id, video_to_packet,
    RtmpPacketSource, AUDIO_STREAM_INDEX, RTMP_TIME_BASE, VIDEO_STREAM_INDEX,
};
pub use amf::Amf0Value;
pub use amf3::Amf3Value;
pub use client::{RtmpClient, RtmpUrl};
pub use error::{Error, Result};
pub use flv::{AudioTag, ModEx, VideoTag};
pub use server::{PublishRequest, RtmpServer, RtmpSession, StreamPacket};