[OSM-dev] 0.6 api - one more time

Tom Hughes tom at compton.nu
Mon May 5 16:01:46 BST 2008

In message <20080505144851.GA15379 at metacarta.com>
          Christopher Schmidt <crschmidt at metacarta.com> wrote:

> So, one thing that I would like to question is whether we really need to
> break backwars compatibility for this change at all.
> Based on my reading, there is only one aspect of the changes in the API
> that forces backwards incompabitibility: the requirement for the client
> to generate a changeset before uploading and provide that changeset
> identifier.
> Now, based on my reading of this, (which could be wrong), if that's the
> only change, there is a way to simply allow 0.5 API clients continue to
> work: If a changeset identifier is not provided, then create a changeset
> automatically.

It isn't the changesets that forced the version change because
you're quite right that we could create implicit changesets if
the client didn't create one.

What sealed it I think was when we decided to make clients indicate
what version of the object that had when making a change, so that the
server could reject the change if the object had been changed since
that client last downloaded.


Tom Hughes (tom at compton.nu)

More information about the dev mailing list