[OSM-talk] Warning : Lint storm ahead !

[Nic Roets]

Before the rails port, it happened frequently (to me at least) that
JOSM and the Applet asked for an object (node / segment / way to be
created) and although it didn't that object was nonetheless created by
the DB. I then restarted the upload (or recreated the node) and hence
another object was created.

This problem is now much worse under rails : I seems to me that
potlatch automatically retries, because there are now HEAPs and HEAPs
(or loads or swarms) of lint in the spot I edited yesterday.

The solution would be to identify objects not by the MySQL assigned
object ID, but instead by a concatenation of a unique client-side
session number (assigned by MySQL) and a new object counter maintained
by that client side app.

Another solution would be for client-side apps to ask for OIDs at the
start of each upload.