overleaf/services/real-time/app/coffee
Shane Kilkelly 6765d03339 Track the isRestrictedUser flag on clients
Then, don't send new chat messages and new comments to those restricted clients.
We do this because we don't want to leak private information (email addresses
and names) to "restricted" users, those who have read-only access via a
shared token.
2019-10-04 10:30:24 +01:00
..
AuthorizationManager.coffee
ChannelManager.coffee add comments 2019-07-24 15:49:29 +01:00
ConnectedUsersManager.coffee minimal fix for undefined connected users 2019-08-16 10:07:30 +01:00
DocumentUpdaterController.coffee refactor subscribe resolution 2019-07-24 14:30:48 +01:00
DocumentUpdaterManager.coffee notify docupdate if the flush is from a shutdown 2019-08-13 17:36:53 +01:00
DrainManager.coffee add log line to draining 2019-08-15 14:41:22 +01:00
Errors.coffee Generate retryable error when hitting rate limits in web 2019-09-02 11:27:04 +01:00
EventLogger.coffee log out of order events now that the rate is lower 2019-07-15 11:14:48 +01:00
HealthCheckManager.coffee
HttpApiController.coffee
HttpController.coffee
RedisClientManager.coffee add logging for redis clients at start up 2019-07-09 14:18:39 +01:00
RoomManager.coffee ignore spurious requests to leave other docs 2019-07-29 15:19:08 +01:00
Router.coffee Generate retryable error when hitting rate limits in web 2019-09-02 11:27:04 +01:00
SafeJsonParse.coffee
Utils.coffee
WebApiManager.coffee Track the isRestrictedUser flag on clients 2019-10-04 10:30:24 +01:00
WebsocketController.coffee Track the isRestrictedUser flag on clients 2019-10-04 10:30:24 +01:00
WebsocketLoadBalancer.coffee Track the isRestrictedUser flag on clients 2019-10-04 10:30:24 +01:00