[OSM-dev] OSMXAPI - Compression?

Raghu Ram raghuram.nadiminti at gmail.com
Fri Mar 28 05:27:12 GMT 2008

Look at http://en.wikipedia.org/wiki/HTTP_compression
In essence the HTTP client has to send the string

Accept-Encoding: gzip,deflate

in its headers. And if the server supports one of the encodings it sends the
follwing response in the response headers

Vary: Accept-Encoding
Content-Encoding: gzip

And btw surveys show that gzip performs the best at xml compression. So how
about making the server to use gzip compression

On Thu, Mar 27, 2008 at 8:23 PM, Tom Hughes <tom at compton.nu> wrote:

> In message <8fcd02310803270732g70f21edcuf694bcf1f28f1451 at mail.gmail.com>
>         80n80n at gmail.com wrote:
> > Once the query has completed the output is streamed directly.
> >
> > I suppose I could build in an option to compress it first.  I don't know
> how
> > much time it would save, but it would certainly free up a bit of
> bandwidth.
> Given that the server is apache mod_deflate can do all the work for
> you given a suitable configuration (and so long as the browser passes
> an Accept-Encoding header to indicate it supports compression).
> BTW, the xapi responses are coming back with a rather bizarre
> content type of "html/xml" at the moment...
> Tom
> --
> Tom Hughes (tom at compton.nu)
> http://www.compton.nu/
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20080328/21c451fa/attachment.html>

More information about the dev mailing list