Undefined behavior with possible data loss if multiple batch managers are started
If multiple VISPA instances are opened, each open a new BatchManager, which will work on the same data! This is especially a problem for the LocalBatchManager, as it executes the jobs itself. Other batch mangers might however also end up in an undefined state. A possible solution would be to use demons / client-server mechanisms, to communicate with the BatchManagers (See: #343 and keep in mind #813). This could be also special interest for Vispa@Web
(from redmine: issue id 1036, created on 2012-05-25 by Tobias.Winchen)