[Tilesathome] *.tah.openstreetmap.org - Why HTTP persistent connections disallowed?

Sebastian Spaeth Sebastian at SSpaeth.de
Tue Nov 3 10:35:43 GMT 2009


GeoJ wrote:
> Hi,
> 
> while playing around with a HTTP proxy I noticed that the tiles at home
> servers *.tah.openstreetmap.org explicitly disallow to use persistent
> connections by sending the header "Connection: close" in the response.
> 
> For a regular http server with small web pages (small number of files
> per webpage) this would not be a problem but those servers also act as
> server for the generated tiles. A common map view in the browser
> consists of ~20-40 tiles and for each tile the browser has to establish
> an separate TCP connection - this is very inefficient and resource
> consuming.

IIRC we did try this earlier, but then a client would be able to occupy
a download slot for a lot longer, making others time out who also want
to get tiles. This is more resource consuming yes, (but the server copes
fine), but it allows more clients to get tiles within a short time span.

I could try to go back to pipelining, but afaik it was causing more
problems than it was solving.

spaetz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/tilesathome/attachments/20091103/0c3c3c19/attachment.pgp>


More information about the Tilesathome mailing list