Hi all, I was asked to design a new django app by a client whose needs are a little bit context-specific.
The purpose of this app is to introduce computer-assisted technologies in a paper-based environment, in the e-Health domain. This client would like to access a central server with a few mobile clients with the constraint of a non-permanent internet connection, because the location of the mobile clients is continuously changing and an internet connection might not always be available. My current idea is based on a portable small server (a nettop, or even a raspberry pi, as the computing power is not a problem for this app) with a django app on it and a wireless access point for providing mobile clients with an always-on portable server reachability. At the same time, I'd like other clients around the world (a very little number, though) to still be able to access a central remote version of the same service, so I'd still deploy the same app (with its own DB replica) within a remote server. I hope I made my client's requirements clear: how would you manage the synchronization between the two DBs, given that both DBs need a write access and that the only relaxation of this constraint is that when the portable server is on, the remote DB might work in a read-only mode (but this is not required). Thanks in advance for any suggestions you'll provide me with. B. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/bb65e66c-4788-4010-9bfe-b8f20e41e5d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
