[Koha-bugs] [Bug 27661] Clarify error for message broker

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27661

--- Comment #21 from Martin Renvoize <martin.renvoize at ptfs-europe.com> ---
(In reply to Marcel de Rooy from comment #13)
> We are advertizing here that we support SQL polling and Rabbit MQ.
> Is that really the way we want to go? Support both ways for any new case
> where we would like to use RabbitMQ?
> The SQL polling has been added to the initial use of RabbitMQ as a fallback
> and probably for building some confidence.
> 
> Since I doubt that we will be supporting both ways, I would propose
> rewording.
> Any thoughts?

I think it would be trivial to drop update the change here at the same time as
deprecating the polling fallback should we do that in the future.

I'm actually wondering if things might go the other way... I was wary of adding
yet another system to run and maintain when we added RabbitMQ personally.. I'm
really not sure we need all that it offers and personally would have preferred
an approach where we started with an SQL based queue and migrated to a bigger
broker only as and when we found we needed it/found that polling was a
performance issue.

I'd also like to drop the 'required' state of the STOMP dependency as we don't
actually require it to function.. we just require it at the moment as we use it
to work out if RabbitMQ is present in the worker daemon.

-- 
You are receiving this mail because:
You are watching all bug changes.