On Sat, Oct 20, 2012 at 11:50 AM, Kolossos <tim.al...@s2002.tu-chemnitz.de> wrote: > Am 17.10.2012 12:39, schrieb Martin Koppenhoefer: > >> OK, but besides of reducing the load on the API the suggested >> behaviour would also be more clearly laid out, at least for everything >> that is not quite small. You won't usually look in detail at a list of >> tens or hundreds of nodes and multiplied by every single version (and >> maybe hundreds of versions). >> >> cheers, >> Martin > > > I would prefer the way of mediawiki to handling versions. The user get a > short list of versions and can select diffs.
Are you talking about the API history call or the /browse/ pages history? I *think* one of the most expensive parts of the /browse/ pages is looking up all the sub-elements to be able to put tag-based icons by nodes and put way names and the "(also part of way <whaever> (xxxxxxxx))" text next to things. This is why the history API call is more likely to return than the /browse/ page in a browser. Toby _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
