Autosave for web players in cloud,

There is a public idea for autosave but this is adressing only webplayer cloud and in particular Web player in TSCL.

We need autosave in cloud of several reasons. The obvious reason is to save changes when the user accidentally closes his web browser or when the connection is lost. Another case is when you upload a data file (which can take uptp 20 minutes or more), edit the dxp and then forgets to save it,  

All those cases has in common that the autosave function should protect for user errors or network problems. Autosave is not needed to protect against server crashes. A server crashed very, very seldom in a strictly controlled environment such as in the cloud,

That means that autosave can be implemented without storing the DXP to the database each time. It is just enough to store it after when some criterias such as when the user session times out or when the user leaves the dxp.  

This would also solve another inconvenience in the product. Now when I save a large DXP I have to wait until it is confirmed stored on disk before I get redirected to the file manager. This is of course completely unnecessary as the user can not do anythng else anyway if the storage fails.

This very basic autosave function would be pretty straight forward to implement and could be spiced up with some more advanced error handling functions later. E..g  with a semaphore system that warns that a file might not have been stored properly due to e.g. a (rare) server crash or the other rare case that two instances of the same DXP has been updated in parallel on two different servers (I a not even sure if that can happen). 

Since I lost a couple of large files un upload already during testing I need this yesterday.