Expand description
This module contains implemented session abstractions.
A session is a high level abstraction that makes it simple to create custom RTMP clients and
servers without having to worry about the exact flow of RTMP messages to perform specific
actions. The session has it’s own ChunkSerializer and ChunkDeserializer so consumers only
have to worry about bytes in and bytes/events out.
A single session represents a single peer in an RTMP connection, so if multiple connections are being managed (in any direction) each connection should have its own, distinct, session instance.
It is also expected that a session has been created after handshaking has been completed.
Structs
A session that represents the client side of a single RTMP connection.
Configuration options that govern how a RTMP client session should operate
A session that represents the server side of a single RTMP connection.
The configuration options that govern how a RTMP server session should operate
Contains the metadata information a stream may advertise on publishing
Enums
Error state when a client session encounters an error Represents the type of error that occurred
Events that can be raised by the client session so that custom business logic can be written to react to it
A single result that is returned when the client session performs an action or receives messages from the server.
The type of publishing being performed or requested
The type of publish request being made
Error state when a server session encounters an error Represents the type of error that occurred
An event that a server session can raise
A single result that is returned when a server session processes some bytes