On Fri, Nov 16, 2012 at 4:13 PM, Federico <federicobo...
> Hi developers,
> Let me first say that, IMHO, this usage of redis is an outstanding
> architectural decision.
> I'm integrating bbb into a RoR app. Logging bbb events in the database was
> very simple, just by subscribing to the redis publication.
> Looking forward to 0.81, where all events will go through redis!
That's the plan. The idea is that the Red5 app and NodeJS app (for HTML5)
can sync with each other by subscribing to redis pubsub.
The work is done in
The idea is that all messages (from Flash client, redis pubsub, FreeSWITCH
ESL) goes in here
The message is processed by
other classes (Presentation, Whiteboard, Chat, etc.) and then a
goes out through
The out gateway will have listeners that forwards the message to Red5 Flash
Client, redis pubsub, and recorder to redis.
The listener for user events that forward to Flash client is
There will be classes for each app (Presentation, Whiteboard, chat,
The one for redis pubsub is in
There's still more work to be done. If anybody can help, then the work gets
> Now to the point:
> 1. Why is the externalUserId not sent in all redis' messages?
Our first playback format was very simple. What we wanted was to just be
able to play the slides with audio. There was no need for externalUserID so
we did not include it.
> 2. Was this a design decision?
> Having the externalUserId in every request will be very useful to avoid
> having to figure out the mapping between external and internal user id
> after the first message.
Agreed. Can you please create an issue? We'll include it as part of the