File rubygem-bunny.changes of Package rubygem-bunny
------------------------------------------------------------------- Tue Aug 6 17:45:11 UTC 2013 - coolo@suse.com - updated to version 0.10.0 This release has one minor **breaking API change**. ### Safe[r] basic.ack, basic.nack and basic.reject implementation Previously if a channel was recovered (reopened) by automatic connection recovery before a message was acknowledged or rejected, it would cause any operation on the channel that uses delivery tags to fail and cause the channel to be closed. To avoid this issue, every channel keeps a counter of how many times it has been reopened and marks delivery tags with them. Using a stale tag to ack or reject a message will produce no method sent to RabbitMQ. Note that unacknowledged messages will be requeued by RabbitMQ when connection goes down anyway. This involves an API change: `Bunny::DeliveryMetadata#delivery_tag` is now and instance of a class that responds to `#tag` and `#to_i` and is accepted by `Bunny::Channel#ack` and related methods. Integers are still accepted by the same methods. ------------------------------------------------------------------- Tue Jul 30 16:01:23 UTC 2013 - coolo@suse.com - updated to version 0.9.8 ### Exclusivity Violation for Consumers Now Raises a Reasonable Exception When a second consumer is registered for the same queue on different channels, a reasonable exception (`Bunny::AccessRefused`) will be raised. ## Changes between Bunny 0.9.6 and 0.9.7 ### Reentrant Mutex Implementation Bunny now allows mutex impl to be configurable, uses reentrant Monitor by default. Non-reentrant mutexes is a major PITA and may affect code that uses Bunny. Avg. publishing throughput with Monitor drops slightly from 5.73 Khz to 5.49 Khz (about 4% decrease), which is reasonable for Bunny. Apps that need these 4% can configure what mutex implementation is used on per-connection basis. ## Changes between Bunny 0.9.5 and 0.9.6 ### Eliminated Race Condition in Bunny::Session#close `Bunny::Session#close` had a race condition that caused (non-deterministic) exceptions when connection transport was closed before connection reader loop was guaranteed to have stopped. ## Changes between Bunny 0.9.4 and 0.9.5 ### connection.close Raises Exceptions on Connection Thread Connection-level exceptions (including when a connection is closed via management UI or `rabbitmqctl`) will now be raised on the connection thread so they * can be handled by applications * do not start connection recovery, which may be uncalled for ------------------------------------------------------------------- Wed Aug 1 05:02:20 UTC 2012 - coolo@suse.com - updated to version 0.8.0 ------------------------------------------------------------------- Tue Jul 10 19:11:09 UTC 2012 - jatan@suse.de - Add provides for rubygem-bunny-0_6 ------------------------------------------------------------------- Tue Jun 5 12:40:45 UTC 2012 - saschpe@suse.de - Fixed license (MIT) ------------------------------------------------------------------- Thu Apr 21 17:32:36 CEST 2011 - berendt@b1-systems.de - initial version (created with gem2rpm-opensuse)
