https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 --- Comment #8 from David Cook <dcook@prosentient.com.au> --- (In reply to Josef Moravec from comment #6)
I think just to polish this functionality would be great start and big progress from what we have now.
Actually, I think that's a really good point. I think in the community we sometimes have a tendency to debate/discuss things to death... which stifles innovation. I think it could be good to get something polished into Koha (maybe just 1 background job using RabbitMQ to start) and then if that is working well then we add more background jobs. I suppose it might be more efficient to have it fully specified before implementing in Koha rather than doing iterative development but... -- Oh, but I think my concerns about multi-tenant environments are important. At a glance, this implementation seems like it would only allow 1 Koha instance talk to 1 RabbitMQ instance. But I think in practice there are many people who run multiple Koha instances on the same server and it would be good if they could share 1 RabbitMQ instance. -- You are receiving this mail because: You are watching all bug changes.