adding option to only get "newer than" - objects #17
Comments
|
Author: immanuel.scholz[at]gmx.de
The second option is much more important. In fact, I think the former isn't necessary anyway if things like the planet.osm snapshot make the round.. |
|
Author: writetodan[at]yahoo.com for this to work, need to have sequential change IDs, as objects can share the same timestamp - i.e. need a version table (as there already is for ways). |
|
Author: tom[at]compton.nu See also #94 which asks for the same thing. |
|
Author: Richard Five years later, we have minutely diffs! |
|
Author: woodpeck Minutely diffs do not fix this particular issue. |
|
Author: iandees A newer-than arg to the map call might be interesting to help cut down on data transfer for clients. |
Reporter: steve[at]fractalus.com
[Submitted to the original trac issue database at 3.25pm, Thursday, 10th November 2005]
An option to grab only those objects that are newer than a specific time would
enable clients to cache data performantly.
"newer than" must return all objects that changed since the given time, so a
last changed timestamp are needed for every object.
Either, the referencing objects of all changed objects are transfered as well.
Then this option is nice as stand alone for viewing only recent changes.
Or it really only transfer those objects that have changed, in which case the
performance is optimal for clients using caches.
Note, that for the second option, this cannot be done correctly with GPX, e.g.
it must be possible to transfer line segments without tracks or property-keys
without any object.
When using the second option with the XML scheme proposed in the wiki, it has to
be allowed, that objects are transfered without their referencing object before
(the clause "There must be no reference to an id, which has not been transfered
yet." is disabled)
The text was updated successfully, but these errors were encountered: