Target release

0.6.4 - 0.6.6

Description

Tomas (from Pohl Data) had some problems related to two vertigo-update(s) running at the same time, this shouldn't happen, and i even thought that i wrote some locking code to avoid it.

That locking code obviously needs to be checked and double checked again, along with the code for locking the main configuration as well as domains before reading/writing.

Maybe it can be included in the test framework mentioned in Vertigo/Bugs/UnitTestingFrameworkForTheEntireLibrary