Ensure that server code is reentrant/threat-safe

In order to be able to allow the implementation of a multi-threaded server, we must not rely on shared data structures that would become subject of race conditions, or provide adequate serialisation.

Review the code with that in mind, document that the respective classes are reentrant or thread-safe where applicable, and consider how we can implement test that verify this also for future changes to the framework.