https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #107 from David Cook <[email protected]> --- Consider reading my (short) comment https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993#c54 It might be better to have Koha code enqueue to a destination of "/koha_kohadev_schedule" and let the message contain the exact details. Then a scheduler (in this case it can just schedule for right now) will take that message and send it (now or in the future at a designated time) to the job-specific queue "/koha_kohadev_batch_biblio_record_modification", which will be read by workers subscribed to that queue. I don't know how big of a change it would be at this point, but it might add some future proofing for when we do have a task scheduler... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
