[OSM-dev] 0.6 API clarifications and corrections

bvh bvh-osm at irule.be
Thu May 15 10:52:45 BST 2008


On Thu, May 15, 2008 at 07:18:30AM -0400, Christopher Schmidt wrote:
> > But one of them will be accepted first and the other will later
> > be judged as sufficiently different, right? So the actually history
> > in the database will have two transitions, one from v1 to v2 and
> > the other from v2 to v3.
> Yes, but the client uploaded version="1", and the server handed back
> version="3". The client couldn't assume that "current_version + 1 ->
> new_version".

That is ok. The server only needs to send you the new version, you
already have the old one. So again no need to have two different
versions in your response.

> > > It is also possible to change the same object multiple times within the 
> > > same changeset, so one single changeset might catapult the object 
> > > version from 1 to 15.
> > Wouldn't it be better then to just throw away consecutive changes to
> > the same object and only keep the last one within each diff?
> This is about changeset serialization, not diffs. (I made the same
> mistake.)

See my other email regarding changeset serialization. (But you also
came to the same conclusion I think)

cu bart




More information about the dev mailing list