> Somehow create a standalone django app that is the same as the online one > and then have it synchronize when it goes back online. Something ala Google > Gears / HTML5. But not done anything like this and I'm not sure how > complicated the synchronizing would be and I'm reluctant to roll out django > installations on loads of laptops.
If you have a JS based HTML 5 app, you could store data into IndexedDB and then sync it all up when they come back online. From an end users point of view it could be pretty seamless as they switch from online to offline. This would not require Django being installed, just using HTML5. > Use a non-django app which might be a bit lighter, eg MS Access or some > sqlite front end and then have that synchronize. Again, similar issues as > above, although. You'll likely have syncing issues whatever system you use. Choose your pain point and remove as many syncing/conflict issues as you can before you start implementing. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
