Richard wrote:
Well, perhaps my feedback gives you arguments in the following direction:
It seems to me, that there has not been installed a correct priority handling on the server.
Edit tasks like Potlatch or JOSM have to be served with highest priority possible other than real time priority. These are the tasks, where data losses imply loss of real work. And these are the tasks where people are waiting online for server response. All other tasks like map display or map generation should have to wait behind those important tasks being served !
Thanks for linking R. Bannister. Was nice to learn about him. You may understand, that running miles is not that popular in Germany, especially since it is not an Olympic discipline.
Have you ever heard of Armin Hary ?
He was the first to run 100 m within 10.0 s. It was often said, if at that time, electronic stopwatches were in use, he would have been the first to run the 100 m under 10 s.
What will happen then ? Do I have to stop working until you have finished analyzing ?
The only thing I can see is the error message, but Potlatch still continues running like nothing has happened. And: Potlatch only says, that an error has occurred, but gives no hints what kind of error (as I remember, since I’ve currently stopped working).
You are right, actually in German translation it sounds quite different than in the original. IÂ’ve read several times the according sentence and tried to find a padlock before I had to deal with the locked ways. When I had the problem, I didnÂ’t remember that sentence to be valid just this very moment.
And once again: The way should be unlocked automatically, as soon as it is connected somewhere else. Nobody will try to connect an irrelevant way. And if he does und doesn’t realize the error, he is a fool. A fool who also is able to unlock the way unintentionally.