https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #12 from Tomás Cohen Arazi <tomasco...@gmail.com> --- (In reply to Marcel de Rooy from comment #11) > (In reply to Katrin Fischer from comment #10) > > (In reply to Marcel de Rooy from comment #9) > > > Do we really need the background jobs ? Or should we refactor these > > > scripts > > > in the direction of AJAX API calls in JavaScript ? > > > > I am not sure if this would also allow reimplementing the scheduler with > > scheduled reports? In my understanding some jobs might not be triggered by > > the GUI. > > OK That's true. I was focused on the forking scripts. IMHO, in either case we need a way to throttle concurrency and server loads. So a task queue is needed. My only doubt is if we should really model the task queue with a message queue. I tried the same Jonathan tried but using AnyEvent::Task and the results where similar, and it only required a unix socket to communicate client and server processes. My suggestion was to use zeromq. But lets see how this goes. Specially in the integration step. I agree with David that this of course would require a single RabbitMQ server so questions: Is there a concept of namespaces? can any Koha instance access other instance's messages? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/