https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 --- Comment #267 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to David Cook from comment #263)
Right now, Koha - even when running Plack - depends on CGI. Using RabbitMQ provides a standard way of breaking our remaining dependency on CGI scripts for long-running tasks.
I am not following this argument. We are not introducing a MQ to eliminate CGI. Imo this is really another topic, not in the scope of this report.
As time passes, more and more of Koha will use the message queue as well. There are many long-running jobs, which would benefit from being placed into the background. This change is about building capacity and improving performance.
So we have an architectural reason for a MQ. And the question is: do we want an optional introduction needing additional fallback code, or dont we postpone making it mandatory (since it will be one day)? -- You are receiving this mail because: You are watching all bug changes.