[Tilesathome] Weird failure of T at H client

[Dirk-Lüder Kreie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

D Tucny schrieb:

> I think his point is that when the server was down, his client died,
> but, that looking at the munin graphs, it appears that most other
> people's seemed to just continue after the return of the server...
> 
> I'm guessing that just deelkar restarting his renderers is enough to
> make take t at h to as fast as the API will allow it, making the graphs
> look like they do...

Heh, I wish ;)

There are circumstances where your client IP gets banned from using the
OSM API altogether (not sure if limited by time or if manual
intervention is required) so an exponential backoff scheme would need to
take this into account.
Also we would need to examine the error code returned more closely, and
perhaps the OSM API can help us by giving better information in the
Human readable part of the error message.

- --

Dirk-Lüder "Deelkar" Kreie
Bremen - 53.0952°N 8.8652°E

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHPVf9FUbODdpRVDwRAvAMAKClzT5jCjvO67azl6UTiXlGyfDbhACgyEPQ
/I8b8KOt+6s4D5gqglJGEEA=
=OZ72
-----END PGP SIGNATURE-----