[OSM-dev] OSM without segments - prototype

[Tom Hughes]

In message <46C975EC.4040400 at bretth.com>
        Brett Henderson <brett at bretth.com> wrote:

> If API scalability is an issue, the most effective change I can think of 
> would be to allow a set of changes to be made via a single API request.  
> This would correspond to a single HTTP request/response each time you 
> hit the update button in JOSM.  This would drastically reduce the number 
> of request/responses through the web server and *if* we were using a 
> database with full transaction support it would reduce database load by 
> grouping changes into single transactions.

I'd love to do that, but it has one really horrible problem - what do
you do if you get halfway through the file and encounter an error... How
do you roll back the changes you have already made?

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/