Tim Alby c1c23e4bee record last author id on document flush ... This is a multi-steps process: * get a update's `user_id` from the metadata * store the `user_id` (`lastUpdatedBy`) and current date (`lastUpdatedAt`) for the document in Redis on every updates * fetch `lastUpdatedAt` and `lastUpdatedBy` from Redis on document flush * send the data to web to be persisted in Mongo		2019-05-02 11:10:02 +01:00
..
DiffCodec
DispatchManager
DocumentManager	record last author id on document flush	2019-05-02 11:10:02 +01:00
HistoryManager
HistoryRedisManager
HttpController	use explicit json content-type to avoid security issues with text/html	2019-02-12 16:45:11 +00:00
LockManager
PersistenceManager	record last author id on document flush	2019-05-02 11:10:02 +01:00
ProjectHistoryRedisManager
ProjectManager	Record a snapshot to mongo when a doc's comments/changes get collapsed	2019-04-11 13:27:46 +01:00
RangesManager	Record a snapshot to mongo when a doc's comments/changes get collapsed	2019-04-11 13:27:46 +01:00
RateLimitManager
RealTimeRedisManager	include a unique id in every message published to redis	2019-03-21 12:10:15 +00:00
RedisManager	record last author id on document flush	2019-05-02 11:10:02 +01:00
ShareJS
ShareJsDB
ShareJsUpdateManager
UpdateManager	record last author id on document flush	2019-05-02 11:10:02 +01:00