[OSM-dev] [OSM-talk] donating read-only api-mirrors

Stefan de Konink stefan at konink.de
Fri Feb 6 23:47:21 GMT 2009

Matt Amos wrote:
> On Fri, Feb 6, 2009 at 8:32 PM, Stefan de Konink <stefan at konink.de> wrote:
>> Matthias Julius wrote:
>>> Is anyone relying on the ascending ID order?
>> Even then; the ordering can be done in SQL.
> not in the two-step scheme that Matthias was suggesting. it might be
> possible using temporary tables, but care would be necessary to work
> around mysql's horrible "can't re-open table" brokenness.

I really don't see how you could fetch *all* ways without the nodes that 
are in the bbox or a join on the table.

>>> To be able to send proper error codes to the client when something
>>> goes wrong halfway down the path the data could be cached on disk and
>>> sent out once it is complete.
>> This is significant overhead. Just stream out, if there is really a
>> problem; just close the current open tag {node,way,relation} and append
>> <error>Whatever</error> after it.
> adding an error element would require a (small) change to all clients
> to support it, which is fine if all the tool authors are willing to
> make the change (or accept a patch).

Yes, but since we are changing protocols soon, error messages would be a 
minor implementation effort ;)


More information about the dev mailing list