M-Files
TaskQueueBackgroundOperationManager since VAF 2.3 no more parallel tasks possible
Since the update of the VAF.Extensions from 1.2 to 1.3 (VAF 2.2 to 2.3), the background tasks that were created using the TaskQueueBackgroundOperationManager can no longer run in parallel. For me it has a big impact on compatibility. Is there anything I haven't considered about?
When the task queue is registered it does not provide any details on the queue type (sequential or concurrent), nor does it provide any explicit value for the maximum concurrency. As such it will use the defaults (concurrent, but one task at a time per server).
It should be possible to expose a property to set the maximum concurrency to something higher, defaulting to 1, which would then be provided as part of a TaskQueueSettings instance when registering the queue. I don't believe this would break anything. That said: it will not ever work exactly the same as the original VAF 1.0 "background operations" due to the way in which the polling for the queues work.
