The Bugzilla server-side extension I released previously has been renamed to bugzilla-push. It can now be found at The main impetus for the name change was that it now supports STOMP in addition to AMQP. It seemed silly to keep “amqp” in the name when it supports multiple protocols.

The reason for adding STOMP support is to keep my message broker options open. While RabbitMQ is pretty nice, it may not meet the needs for once it gets out of prototype mode. All open source brokers (HornetQ, Apache ActiveMQ & Qpid, Redhat MRG, etc) have pledged to support AMQP eventually, but many have not implemented it. Most have implemented STOMP though, as the protocol is both stable and simple. The extension now gives the Bugzilla administrator the option of choosing which protocol to use based on their requirements.

Notable changes since I last blogged:

  1. Pluggable backends with optional CPAN dependencies. If you don’t want to use AMQP, you don’t need to have those dependencies installed
  2. Added simple support for message security. This was a major hurdle for getting bugzilla-push rolled out on I intend to beef it up more in the coming weeks as well
  3. Fixed a bug where false values were being sent as “0” in the JSON messages instead of JSON’s false
  4. Fixed support for using vhosts that are not “/” (the AMQP default)

Planned in the next week:

  1. Supporting YAML for message encoding
  2. Supporting Python’s pickle for message encoding
  3. Get the extension rolled out on
  4. Test, test, test
  5. Ask for security review from Mozilla’s web security team
Tagged with: