View Source Membrane.RTMPServer.ClientHandler behaviour (Membrane RTMP plugin v0.28.1)

A behaviour describing the actions that might be taken by the client handler in response to different events.

Summary

Types

Type representing the user defined state of the client handler.

t()

A type representing a module which implements Membrane.RTMPServer.ClientHandler behaviour.

Callbacks

Callback invoked when the socket connection is terminated. In normal conditions, handle_delete_stream is called before this one. If delete_stream is not called and connection_closed is, it might just mean that the connection was lost (for instance when TCP socket is closed unexpectedly).

The callback invoked when new piece of data is received from a given client.

Callback invoked when the RMTP stream is finished.

The callback invoked when the client handler receives a message that is not recognized as an internal message of the client handler.

The callback invoked once the client handler is created. It should return the initial state of the client handler.

The optional callback invoked when the client handler receives RTMP message with metadata information (just like a resolution or a framerate of a video stream). The following messages are considered the ones that contain metadata

Functions

Returns a specification to start this module under a supervisor.

Makes the client handler ask client for the desired number of buffers

Types

@type state() :: any()

Type representing the user defined state of the client handler.

@type t() :: module()

A type representing a module which implements Membrane.RTMPServer.ClientHandler behaviour.

Callbacks

Link to this callback

handle_connection_closed(state)

View Source
@callback handle_connection_closed(state :: state()) :: state()

Callback invoked when the socket connection is terminated. In normal conditions, handle_delete_stream is called before this one. If delete_stream is not called and connection_closed is, it might just mean that the connection was lost (for instance when TCP socket is closed unexpectedly).

It is up to the users to determined how to handle it in their case.

Link to this callback

handle_data_available(payload, state)

View Source
@callback handle_data_available(payload :: binary(), state :: state()) :: state()

The callback invoked when new piece of data is received from a given client.

Link to this callback

handle_delete_stream(state)

View Source
@callback handle_delete_stream(state :: state()) :: state()

Callback invoked when the RMTP stream is finished.

@callback handle_info(msg :: term(), state()) :: state()

The callback invoked when the client handler receives a message that is not recognized as an internal message of the client handler.

@callback handle_init(any()) :: state()

The callback invoked once the client handler is created. It should return the initial state of the client handler.

Link to this callback

handle_metadata({}, state)

View Source (optional)
@callback handle_metadata(
  {:metadata_message,
   Membrane.RTMP.Messages.OnMetaData.t()
   | Membrane.RTMP.Messages.SetDataFrame.t()},
  state()
) :: state()

The optional callback invoked when the client handler receives RTMP message with metadata information (just like a resolution or a framerate of a video stream). The following messages are considered the ones that contain metadata:

  1. OnMetaData
  2. SetDataFrame

Functions

Returns a specification to start this module under a supervisor.

See Supervisor.

Link to this function

demand_data(client_reference, how_many_buffers_demanded)

View Source
@spec demand_data(pid(), non_neg_integer()) :: :ok

Makes the client handler ask client for the desired number of buffers