view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

        - Stop defining a _return_cb value when not using the mandatory
          or immediate flags when publishing a message. This means that
          if you're not using these flags, but are using an infinite set
          of routing keys, then you won't leak infinite RAM.
          Currently if you do use these flags and infinitely variable
          routing keys, we still have a problem as we leak callbacks.
          RT#79511

1.08    Mon Aug 27 08:43:00 2012
        - Improve Data::Dumper options for protocol dumps (Chip Salzenberg)
        - More thoroughly eliminate memory leaks on incoming messages
          (Chip Salzenberg)
        - Properly handle channel close: Ensure pending requests fail
          immediately (Chip Salzenberg)

1.07    Tue Aug 21 15:47:00 2012
        - Fix dist by putting missing version numbers back into
          all the modules.

1.06    Tue Aug 21 15:10:00 2012

lib/AnyEvent/RabbitMQ.pm  view on Meta::CPAN

use strict;
use warnings;
use Carp qw(confess croak);
use Scalar::Util qw(refaddr);
use List::MoreUtils qw(none);
use Devel::GlobalDestruction;
use File::ShareDir;
use Readonly;
use Scalar::Util qw/ weaken /;

require Data::Dumper;
sub Dumper {
    local $Data::Dumper::Terse = 1;
    local $Data::Dumper::Indent = 1;
    local $Data::Dumper::Useqq = 1;
    local $Data::Dumper::Deparse = 1;
    local $Data::Dumper::Quotekeys = 0;
    local $Data::Dumper::Sortkeys = 1;
    &Data::Dumper::Dumper
}

use AnyEvent::Handle;
use AnyEvent::Socket;

use Net::AMQP 0.06;
use Net::AMQP::Common qw(:all);

use AnyEvent::RabbitMQ::Channel;
use AnyEvent::RabbitMQ::LocalQueue;

xt/04_anyevent.t  view on Meta::CPAN

use Test::More;
use Test::Exception;
use Data::Dumper;
use version 0.77;

use FindBin;

my %server = (
    product => undef,
    version => undef,
);

my %conf = (