James Allen cde5144c42 Retry updates that have not been acknowledged. ... If we do not get a reply from the server acknowledging our update after 5 seconds, send it again. If it never got to the server, this is like normal. If the update got to the server, but we never received the ack then we need to rely on ShareJs's duplicate handling. We set the dupIfSource parameter on any retried updates which let ShareJs know that it's a dup if we already have an op with this version number and client id. The doc-updater and real-time services need changes to correctly send another ack only to the submitting client in the case of a duplicate update.		2015-11-19 12:04:12 +00:00
..
controllers	Report unsaved changes after 60 seconds	2015-11-18 15:23:23 +00:00
directives	Remove uneeded and now wrong Sentry error capturing	2015-09-08 11:48:39 +01:00
sharejs	Put in client side check for document getting too long	2015-11-06 12:51:43 +00:00
Document.coffee	Retry updates that have not been acknowledged.	2015-11-19 12:04:12 +00:00
EditorManager.coffee	Put in client side check for document getting too long	2015-11-06 12:51:43 +00:00
ShareJsDoc.coffee	Retry updates that have not been acknowledged.	2015-11-19 12:04:12 +00:00