Janus RabbitMQ transport plugin.
- Author
- Lorenzo Miniero loren.nosp@m.zo@m.nosp@m.eetec.nosp@m.ho.c.nosp@m.om
- Copyright
- GNU General Public License v3 This is an implementation of a RabbitMQ transport for the Janus API, using the rabbitmq-c library (https://github.com/alanxz/rabbitmq-c). This means that this module adds support for RabbitMQ based messaging as an alternative "transport" for API requests, responses and notifications. This is only useful when you're wrapping Janus requests in your server application, and handling the communication with clients your own way. At the moment, only a single "application" can be handled at the same time, meaning that Janus won't implement multiple queues to handle multiple concurrent "application servers" taking advantage of its features. Support for this is planned, though (e.g., through some kind of negotiation to create queues on the fly). Right now, you can only configure the address of the RabbitMQ server to use, and the queues to make use of to receive (to-janus) and send (from-janus) messages from/to an external application. As with WebSockets, considering that requests wouldn't include a path to address some mandatory information, these requests addressed to Janus should include as part of their payload, when needed, additional pieces of information like
session_id
and handle_id
. That is, where you'd send a Janus request related to a specific session to the /janus/<session>
path, with RabbitMQ you'd have to send the same request with an additional session_id
field in the JSON payload.
- Note
- When you create a session using RabbitMQ, a subscription to the events related to it is done automatically through the outgoing queue, so no need for an explicit request as the GET in the plain HTTP API.
transports