[OSM-dev] Minute Diffs Broken

Brett Henderson brett at bretth.com
Tue May 5 12:34:24 BST 2009

Matt Amos wrote:
>> As
>> for JOSM, I have already heard complaints, and people have asked how
>> they can go back to the old non-changeset upload, because they
>> explicitly *want* as much as possible of their changeset to upload, and
>> are pissed off when the whole changeset fails because it contains a
>> change to some monster object that is changed very often.
> can JOSM split the single upload into multiple uploads within the same
> changeset? perhaps having a tunable parameter to isolate "large" items
> into their own separate upload?
> there is no reason why one save = one upload = one changeset.
> and this will help with the problem that Brett is seeing, which
> might(*) be down to the following:
> 1. user on a slow connection hits "save", changeset created, client
> begins diff upload
> 2. server starts transaction
> 3. client sends first element, which the server parses and saves
> 4. ... client and/or network slowness cause 5 mins to pass ...
> 5. client ends the diff
> 6. server ends the transaction
> because we're assigning timestamps in rails (at step 3), but the rows
> only become visible at step 6, the delay between the end of the
> transaction and the timestamp on the element could be up to 24h, in
> theory.
I was under the impression that the transaction is only started once the 
diff is fully uploaded.  Is that not the case?  Or is that the bit 
you're unsure about?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20090505/b41cbdc7/attachment.html>

More information about the dev mailing list