About 1 I am sure Jonathan has something to day because of the new routing features.
About 2. Make sure your database tables have a UUID field. When exporting/importing web2py will use it to rebuild references (the ids will not be synced but you can write a simple program to fix references given the UUIDs). It is on my todo list to improve support for this type of issues. Massimo On Jan 30, 10:33 am, VP <vtp2...@gmail.com> wrote: > I have never configured an app like this so I have no idea how this is > done. So, any help or pointer is greatly appreciated. > > Basically, I have an app. If it is hosted in the US, then access in > Asia will be slow. And conversely, if it is hosted in Asia, US access > will be slow. So, I think the best strategy is to host it both in > Asia and the US. > > Ideally, this will be transparent to users. The simplest > configuration I can think of this having 2 domains: domain1.com and > domain2.com; each being hosted in US and Asia, respectively. And > depending on users' geolocation based on IP addresses, they will be > redirected to either domain. > > Two problems: > > 1. the appearance of domain1.com and domain2.com is not transparent > enough. Is there a better way? > > 2. maintaining consistency between the 2 databases. Does web2py have > support for replications of one app like this? > > Thanks.
