https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #259 from Jonathan Druart <[email protected]> --- (In reply to Julian Maurice from comment #258) > (In reply to Marcel de Rooy from comment #257) > > Actually not. As you say, we could run without MQ. But since we want a > > message queue anyway, this could be a nice first start. > That's a thing that is still not clear for me. For what other purpose do we > need a message queue ? For now: all background jobs, and a task scheduler. But that can be extended to other things if we want (like indexing, sending emails, etc.). With a configuration system we could add the capacity to define rules like "execute all the background jobs that does XXX", or "don't execute background jobs during opening hours". Also we could have several workers, each doing something specific, and have them running on a dedicated server. > > What I do not like, is writing two blocks: code with MQ en code without. > I do not like it either, but compared to forcing hundreds of users to > install a new dependency, it doesn't look too bad. The idea was to not reinvent the wheel and use one solution that demonstrated its effectiveness. We could write our own server if we wish. In this implementation (there have been others previously) I decided to make things as simple as possible. -- 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/
