> Since the solution you made doesn't scale either. (Try browsing any city/town in The Netherlands.) How is it an improvement?
Well while http://osmlab.github.io/latest-changes is not fast right now there's a clear and scalable path to make it fast. Speeding up /latest-changes is much simpler as you'll never have to include history. Essentially what we'd need is a tiled data rendition of the latest status of OSM data. No history. Clearly, creating a tiled data source is probably not just a weekend project either but it's conceptually a solved problem in OSM. On Fri, May 3, 2013 at 10:05 AM, Cartinus <carti...@xs4all.nl> wrote: > On 05/03/2013 02:21 PM, Alex Barth wrote: > > Pawel, i do not understand how the New History Tab will scale and how it > > will be fast. Right now it's slow. > > Since the solution you made doesn't scale either. (Try browsing any > city/town in The Netherlands.) How is it an improvement? > > -- > --- > m.v.g., > Cartinus > > _______________________________________________ > dev mailing list > dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/dev >
_______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
