-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lazy channels #291
Comments
I think it could be implemented. I would welcome a PR on that |
@postalservice14 wasn't this solved with #332 ? |
@nubeiro no, even with the lazy socket connections, it still connects when you open a channel. Here the user is asking that the channel not be opened until it is used, not when it is created. Sounds pretty easy to do... I can look into creating a PR. |
Closing due to inactivity. Please reference this issue if a PR is opened for this feature. |
is it possible to make channels from a
AMQPLazyConnection
lazy aswell?so the channel is only opened when its used...
currently creating a channel directly connects (which is needed to get a channel id) to the cluster. but maybe this step could be made lazy?
my use-case is logging. (i use Monolog and an AMQP Handler). A Message is not always delivered, but the connection and channel is always (needless) opened.
The text was updated successfully, but these errors were encountered: