https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32395
--- Comment #2 from David Cook <[email protected]> --- (In reply to Jonathan Druart from comment #0) > Why don't we simply pass the job_id to the broker, then retrieve the > parameters from the DB in the worker? In theory, a loosely coupled message consumer might not have database access to the app, so you'd want to encapsulate everything it needs in the message. However, the system designed for Koha is tightly coupled, so yeah... we could just pass the job_id in the message and have the worker fetch the details. It adds more database I/O, but it probably wouldn't be significant. In some cases, it could actually be more efficient. I don't know what the best practice is, and I imagine we should just do whatever makes sense for us. -- You are receiving this mail because: You are the assignee for the bug. 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/
