[OSM-dev] Data corruption :) II

[Kai Krueger]

On 24/11/08 12:44, Tom Hughes wrote:
> Stefan de Konink wrote:
>    
>> Tom Hughes wrote:
>>      
>> Minutely diffs work perfect. The NL crew is already creating a minutely
>> diff tile cache invalidator; where statitics were already implemented.
>>      
>
> That would be a backward step - we have perfect synchronisation at the
> moment so why move to a situation where you may get old data, even if
> only a few minutes old?
>    
If there was no way to get the uptodate data then yes it would be a step 
backwards, but for many applications that is perfectly fine, I would 
think even for some editing with josm. Not that that would solve the 
issue of the planed maintenance downtime of the main server anyway.
>    
>>> + loss of control unless all proxy targets are maintained by
>>>    the OSM admin team
>>>        
>> The OSM admin team maintains the proxy. And targets get checked if they
>> have the latest minutely's every hour ->  if not, remove from pool.
>>      
>
> Absolutely not. That way leads to chaos. We know this from the t at h proxy
> experience where there was always at least one server that didn't seem
> to be working.
>    
Well, I guess we will soon find out how much chaos it will cause to have 
multiple read only databases managed by different people, with there 
being multiple read only map apis running off the minutely diffs...

Kai