A BarrierController service to allow start/stop dependecies triggered by notifications

In a nutshell, create a service controlling (starting/stopping) a secondary barrier service, on the reception of triggering events (e.g. server startup/shutdown).

Other services can in turn depend on the barrrier service (and follow it's starting/stoping lifecycle) using a simple <depends> element.

See the associated references