AnyEvent-RabbitMQ

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
1.16  Sat Apr 12 14:42:00 BST 2014
        - Doc fixes (Mark Ellis)
        - Fix leak when calling ->close + tests (Peter Haworth)
 
1.15  Mon Jul 1 12:35:00 BST 2013
        - Fix paper-bag bug in connection close - calling nonexistent method.
 
1.14  Fri Jun  7 08:54:00 BST 2013
        - Fix paper-bag bug in heartbeat - always lost heartbeat even on
          active connections
        - on channel close, automatically call on_return callbacks for any
          publishes that are waiting
        - maintain more state around opening and closing to avoid hang/race
          when server sends Close after client does (this is possible!)
        - cope with AMQP quirk that in confirm mode, returned messages are
          *also* acked/nacked
        - document $channel->publish
 
1.13  Thu May  2 16:48:58 PDT 2013
        - Require Net::AMQP 0.06 to:
           + Get consume cancel notifications (e.g. queue deletion)

Changes  view on Meta::CPAN

100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
1.09   Mon Feb 25 12:03:00 2013
        - Support AMQP heartbeat.
 
        - Support AMQP 0.9 standard. (Chip Salzenberg)
 
        - 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

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

153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
}
 
sub _closed {
    my $self = shift;
    my ($frame,) = @_;
    $frame ||= $self->_close_frame();
 
    return if $self->{_state} == _ST_CLOSED;
    $self->{_state} = _ST_CLOSED;
 
    # Perform callbacks for all outstanding commands
    $self->{_queue}->_flush($frame);
    $self->{_content_queue}->_flush($frame);
 
    # Fake nacks of all outstanding publishes
    $_->($frame) for grep { defined } map { $_->[1] } values %{ $self->{_publish_cbs} };
 
    # Report cancelation of all outstanding consumes
    my @tags = keys %{ $self->{_consumer_cbs} };
    $self->_canceled($_, $frame) for @tags;

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

1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
typically L<Net::AMQP::Protocol::Basic::Nack> or L<Net::AMQP::Protocol::Channel::Close>.
 
=item on_return
 
In AMQP, a "returned" message is one that cannot be delivered in compliance with the
C<immediate> or C<mandatory> flags.
 
If in confirm mode, this callback will be called with the frame that reports message
return, typically L<Net::AMQP::Protocol::Basic::Return>.  If confirm mode is off or
this callback is not provided, then the channel or connection objects' on_return
callbacks (if any), will be called instead.
 
NOTE: If confirm mode is on, the on_ack or on_nack callback will be called whether or
not on_return is called first.
 
=back
 
=head2 cancel
 
Cancel a queue subscription.