Skip to content

forget server-generated queue name on disconnect#4

Open
cakirke wants to merge 3 commits intosuretec:masterfrom
cakirke:forget-option
Open

forget server-generated queue name on disconnect#4
cakirke wants to merge 3 commits intosuretec:masterfrom
cakirke:forget-option

Conversation

@cakirke
Copy link
Contributor

@cakirke cakirke commented Dec 13, 2015

server-generated queue names may not be accessible
after disconnect/reconnect due to server permissions.

https://rt.cpan.org/Ticket/Display.html?id=92939

server-generated queue names may not be accessible
after disconnect/reconnect due to server permissions.

https://rt.cpan.org/Ticket/Display.html?id=92939
@abraxxa
Copy link
Contributor

abraxxa commented Jan 1, 2016

I finally took the time to look into it, sorry for the delay!
Do you think the new attribute queue_forget is required and it can't be handled internally without expanding the api?
I'm thinking about a private attribute or method which returns true or false depending on the queue_name and some of the other attributes defined in ::Role::DeclaresQueue.
If that's not sufficient for some use case we can still expose the setting.

@cakirke
Copy link
Contributor Author

cakirke commented Jan 1, 2016

my main concern was that this capability can result in lost (or at least unavailable to the client) messages. wanted the client to have to specifically enable the behavior, rather than it silently being enabled by default.

my $self = shift;
if ((!$self->_requested_queue_name) &&
($self->_has_queue_name && $self->queue_forget)) {
warn('FORGET ' . $self->queue_name);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove this warning

@cakirke
Copy link
Contributor Author

cakirke commented Mar 31, 2016

made requested changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants