https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15032
--- Comment #35 from David Cook <[email protected]> --- (In reply to Tomás Cohen Arazi from comment #34) > This is worth discussing in koha-devel, and IRC meeting or Marseille, but I > think we should have a job queue in the lines of what David proposes. And I > would add maybe the use of ZeroMQ to possibly notify other services. I agree about opening up the discussion in another forum like koha-devel, IRC, or Marseille. I'm intrigued by the use of ZeroMQ. How do you see that working, Tomás? When I first started thinking about background processing, I thought using a message queue would be a good idea. Since then, I've used an embedded ActiveMQ with the Fedora repository a bit, but that publishes notifications about record changes. Celery uses a message queue for sending out tasks and then it can use a backend like Redis for storing task results. I think if we use a database for a job queue, that would replace the message queue? Or are you meaning using a message queue for notifying other services like an indexer that there are imported records to index? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] 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/
