It is harder to build because there is added functionality. You have to replace auto ID generation, which isn't too complicated. I'm not sure what you mean about robustness.
Another issue this would cause is a bigger time delay on the server. I don't think it would be a good idea unless we really need common ids across servers. If so this has the benefit that no code changes except in the assignment of ids on the server. Sent from my iPhone On Sep 25, 2012, at 11:36 AM, Jochen Topf <joc...@remote.org> wrote: > On Mon, Sep 24, 2012 at 09:11:34AM -0700, Dave Sutter wrote: >> This is a very interesting thread and I need a little more time to >> understand what is in it so far. I do want to make one technical >> comment. It is possible to to have multiple databases and still have >> unique IDs across them. An ID server can be set up to create the IDs. >> When one database creates a new object it requests an ID from the ID >> server rather than creating an ID locally. (And of course, if you are >> creating a lot of IDs, you would make one request to the ID server in >> bulk to get all the IDs needed.) > > Yes, but it makes the whole system harder to build and less robust. > > Jochen > -- > Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298 _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
