有没有办法离线记录用户的活动并在线时更新它们？ [关闭]

Question

I just want to allow users make modification offline with insecure data. Namely modifying their profile name, add new content (page), photos and so forth. When they come online all these activities must be updated accordingly in the online server.

I need some vast ideas on this. It's going to be a web app, mostly sort of personal website.If I were to do this app, should I ensure they have mysql and wamp server installed so that offline changes can be recorded in the local host?

I refer to few forums and some of them mentioning html5 localstorage. Here's one of them: Mobile site/app - capture data offline and push to live database

The site to be developed mainly in PHP, MYSQL, HTML5 and JQUERY.

Answer 1

If you don't want to bother your users on how to install some programs in order to store their data while offline - (this process should flow unnoticed or with less pain for the user as possible) I suggest you going for LocalStorage - If you're fine with 10MB (Chrome and Firefox, 5MB on mobile) of user disk quota.

Need more space?

Cache API as an interface of the ServiceWorker API

A service worker is an event-driven worker registered against an origin and a path. It takes the form of a JavaScript file that can control the web page/site it is associated with, intercepting and modifying navigation and resource requests, and caching resources in a very granular fashion to give you complete control over how your app behaves in certain situations (the most obvious one being when the network is not available.)

IndexedDB :

• https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB
• https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Basic_Concepts_Behind_IndexedDB
• https://hacks.mozilla.org/2012/02/storing-images-and-files-in-indexeddb/
• https://github.com/jonnysmith1981/getIndexedDbSize Calculate the IDB size!

Worth knowing that (FF at least) all IndexedDB bases (from multiple sources/websites) cannot take more than 50% total disk size - and from that size one IDB cannot take up more than 20%. Also, according to Least Recently Used Policy, if the databases available space gets full, the browser can (and will) kill an IndexedBD.

Note that for older browsers that do not support IndexedDB you might want to use a shim to fallback to Web SQL Database (which is no longer maintained)