You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
QueueRunner for multi server processing of a longer running queue
It'd be good to be able to configure the QueuedJobService implementation that is used for each runner. At the moment they always return QueuedJobService::singleton() via BaseRunner::getService().
We could change this to use something configuration based, for example:
There's other places where the service class is loaded too, so we'd also need to consider how to load the right job service in various points of the API - this example would only work when loaded from runners, and we don't want to redefine DI config in multiple places.
It's also worth noting that the way the config works at the moment is that the QueuedJobService class defines the runner as a dependency of it, so really BaseRunner::getService() should be returning the class that it's injected into.
The text was updated successfully, but these errors were encountered:
If my project has two separate runners:
DoormanRunner
for immediate queue processingQueueRunner
for multi server processing of a longer running queueIt'd be good to be able to configure the QueuedJobService implementation that is used for each runner. At the moment they always return
QueuedJobService::singleton()
viaBaseRunner::getService()
.We could change this to use something configuration based, for example:
There's other places where the service class is loaded too, so we'd also need to consider how to load the right job service in various points of the API - this example would only work when loaded from runners, and we don't want to redefine DI config in multiple places.
It's also worth noting that the way the config works at the moment is that the QueuedJobService class defines the runner as a dependency of it, so really
BaseRunner::getService()
should be returning the class that it's injected into.The text was updated successfully, but these errors were encountered: