[OSM-dev] [OSM-talk] Handling of towns with different or alternative names

[Richard Fairhurst]

Dave Stubbs wrote:
> I've just done some research on this.

*applauds*

Really interesting. 

> To mitigate: save up writes in potlatch... try not to send any 
> updates with others already pending (that should happen 
> already anyway)

Indeed it should: Potlatch expressly won't upload a way until any pending
uploads of that way return.

I guess this is a plausible scenario:

1. User draws new way A, deselects
2. [Potlatch sends way A to upload]
3. User draws new way B, branching off a new node inserted into way A
4. [Potlatch queues new version of way A, because it can't upload it until 2
returns]
5. [Potlatch queues way B, because it doesn't know the 'branching' node ID
until 4 returns]
6. [Big blocking operation finishes on server; way A written to db,
returning success code to Potlatch]
7. [Potlatch immediately despatches new upload of way A from 4]
8. [New upload executes in same second as 6, triggering bug in Rails code as
described]

For the benefit of others - consensus on IRC seems to be that the
requirement for version numbers in 0.6 may mean we can remove the code that
causes the bug.

cheers
Richard
-- 
View this message in context: http://www.nabble.com/Re%3A--OSM-talk--Handling-of-towns-with-different-or-alternative%09names-tp21697397p21708991.html
Sent from the OpenStreetMap - Dev mailing list archive at Nabble.com.