[OSM-dev] HTTP OSM Server

[Dick]

Frederik Ramm <frederik <at> remote.org> writes:
> The OSM server *is* using only HTTP.
> 
> > The advantages are:
> > - There are a lot of fast HTTP mirrors
> > - The OSM server is quite busy and not reliable for large requests
> 
> Are you aware of Xapi, ROMA, and Trapi? Trapi, especially, stores OSM 
> data snippets in a tiled manner in the file system and can thus serve 
> data for specific tiles very quickly. See the appropriate Wiki pages. 
> Xapi is written in M, ROMA and Trapi are written in Perl.
> 
> Bye
> Frederik

Frederik,

Thanks for your quick reply, I didn't know the existence of Trapi, it shares a
lot of my ideas. But it doesn't scale as well (with loads of small files) and
still requires 8 GB disk usage. But I'm sure I can learn something from Trapi :-)

I'm sorry my post wasn't really clear about what a meant with HTTP OSM Server,
it's HTTP -only- without -any- server side scripting. All planet-osm.bz2 mirrors
will be capable to host my API :-)

Dick