On Wed, May 13, 2009 at 12:36 AM, Frederik Ramm <[email protected]> wrote: > To be just slightly more constructive, the least invasive way of > querying the API for new data only without changing the code would be to > make multi-GETs for batches of object IDs just above the highest known > object ID. That would probably not disrupt services if done by one user, > but then if one user is allowed to do it, what can we say if 10 others > wanted to do the same?
the least invasive way is to use the minutely diffs, as it doesn't touch the API or DB servers at all. > Probably the best way to have a live feed - and a technique that has > been discussed on dev about two years ago - would be to have the rails > code log all successful database operations into a file which could then > be retrieved by an independent daemon and fed into whatever distribution > network you want. That would be about the same thing that database > replication does, just on a higher level. given that there are more efficient ways of doing the database replication than aggregating these feeds from all the different API servers into a coherent whole, i think its probably better to continue creating the feed (i.e: diffs) from the database. unless, of course, you're talking about twittering the updates. that would be teh moar ;-) cheers, matt _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
