Hi. I think that the auto update feature of the ManagedResourceStore could be bad in some cases. I think an option to enable/disable this option on the fly would be need it.
As is stated in docs: "An automatic update is started each time Gears intercepts and serves a request from a ManagedResourceStore". Example when this is bad. There is an application with offline functionality that is working fine. User X comes and syncs all his data (that is a coplex data collection with lots of offline code and a complex database structure). Next day, a major update is done to the the application, update that changes entirely the db structure and way how data are handle. On the server side was written code that will support synchronization with the older versions of the code. Offline mode is composed from 2 big parts: offline database and offline code (mainly javascript code, stored in js files). After the update, server supports synchronization with old code/db and new code/db. But when user X enters again on the site, (he is now connected to internet), ManagedResourceStore will get the new js files automatically and when he tries to sync to online all will crash, because old DB with new code is not working. Due the complexity of the changes, converting offline data to new data on local machine is nearly impossible. This is why I think that an option to disable autoupdate would be nice. What you think? I am missing something?
