On Fri, 06 Feb 2009 15:31:10 +0100, Stefan de Konink <ste...@konink.de> wrote: > marcus.wolsc...@googlemail.com wrote: >> On Fri, 06 Feb 2009 15:16:28 +0100, Stefan de Konink <ste...@konink.de> >> wrote: >>> Florian Lohoff wrote: >>>> API 0.7 should contain a "referral" as LDAP does - So a client could >>>> connect to a cluster of read-only copies and once you write to it you >>>> get a referral to the master database. Synchronization is a big issue >>>> here but it should be a good point for scalability ... >>> I wonder; could we solve this by just sending the history table with a >>> certain key? >> >> What for? >> Your have a version-attribute that tells the server what >> version your chances are based on. > > In that case you could require all the data from that version on :) > Hence have your own mirror with version history :)
I understood "referral" in a way that the client is told to direct all write-queries to the main-api -server. That one of cause can tell you the for any entity you upload the version-number given by the client is no longer the latest version and provide the latest version of such entities. Marcus _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
