Leonardo Crauss Daronco 5d1fb4c168 HTML5 client authentication using redis and the new messages ... The client sends a 'validate_auth_token_request' to the server, that waits a 'validate_auth_token_reply' response from bbb-apps to pass to the client. Still have to get info from /api/enter, for now the meetingId and userId are hard-coded in the client (AuthenticationModel).		2014-04-24 17:39:59 -04:00
..
bbblogger.coffee	Move log path to the config file	2014-04-23 16:39:42 -04:00
clientproxy.coffee	HTML5 client authentication using redis and the new messages	2014-04-24 17:39:59 -04:00
controller.coffee	HTML5 client authentication using redis and the new messages	2014-04-24 17:39:59 -04:00
logger.coffee	- move the html5 client out of labs	2014-01-06 08:44:15 -08:00
messagebus.coffee	HTML5 client authentication using redis and the new messages	2014-04-24 17:39:59 -04:00
modules.coffee	- move the html5 client out of labs	2014-01-06 08:44:15 -08:00
redis_action.coffee	- move the html5 client out of labs	2014-01-06 08:44:15 -08:00
redis_keys.coffee	- move the html5 client out of labs	2014-01-06 08:44:15 -08:00
redis_publisher.coffee	minor changes	2014-04-04 14:26:09 +00:00
redis_websocket_bridge.coffee	minor changes	2014-04-04 14:26:09 +00:00
redispubsub.coffee	HTML5 client authentication using redis and the new messages	2014-04-24 17:39:59 -04:00
utils.coffee	- move the html5 client out of labs	2014-01-06 08:44:15 -08:00