moq-hls 0.5.0

//! HLS / LL-HLS <-> MoQ gateway.
//!
//! Bridges HLS (and Low-Latency HLS) and [`moq_net`] broadcasts in both
//! directions, mirroring the WHIP/WHEP split in `moq-rtc`:
//!
//! - [`import`] pulls a remote HLS master/media playlist and publishes its CMAF
//!   segments into MoQ (an HTTP *client* that *publishes*).
//! - [`server`] serves HLS playlists, DASH manifests, and CMAF segments over
//!   HTTP for MoQ broadcasts (an HTTP *server*). It subscribes only to each
//!   broadcast's catalog and timeline tracks; media bytes are FETCHed from
//!   the relay one group at a time, only when a segment is actually requested.
//!   It serves every request; gate access by layering your own middleware onto
//!   [`Server::router`](server::Server::router).
//!
//! All CMAF byte handling (import via [`moq_mux::container::fmp4::Import`],
//! export via [`moq_mux::container::fmp4::Muxer`]) lives in `moq-mux`; this
//! crate owns the HLS playlist and DASH manifest generation, the
//! timeline-driven playlist window, and the HTTP surface.

#![warn(missing_docs)]

mod error;
pub mod export;
pub mod import;
#[cfg(feature = "server")]
pub mod server;

pub(crate) use error::status_retryable;
pub use error::*;
#[cfg(feature = "server")]
pub use server::Server;

/// Re-export of the HTTP stack behind the export server, so consumers can name the
/// types that surface through [`Server::router`] (and layer their own middleware on
/// it) without adding their own axum dependency and risking a version mismatch.
/// `axum::http` covers the `http` crate types too. A major axum bump is therefore a
/// breaking change for this crate.
#[cfg(feature = "server")]
pub use axum;