Skip to content
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

Expose Connection on eventloop initialization #608

Closed
sushi-shi opened this issue Apr 13, 2023 · 0 comments · Fixed by #611
Closed

Expose Connection on eventloop initialization #608

sushi-shi opened this issue Apr 13, 2023 · 0 comments · Fixed by #611
Labels
stale Not moving forward; blocked

Comments

@sushi-shi
Copy link
Contributor

sushi-shi commented Apr 13, 2023

This would allow calling different initialization routines (e.g. using http proxy).

Though because EventLoop does reconnection inside it, this won't be enough. As the same routine needs to be called every time we reconnect to the server.
So I can either:

  • add support for proxy directly;
  • provide a callback which is going to be called everytime we connect to the socket.

I am willing to implement it.

sushi-shi added a commit to sushi-shi/rumqtt that referenced this issue Apr 20, 2023
Signed off: Ivan Vaitusionak

Issue: bytebeamio#608

Attribute: Ivan Vaitusionak
@stale stale bot added the stale Not moving forward; blocked label May 5, 2023
@yatinmaan yatinmaan linked a pull request May 8, 2023 that will close this issue
2 tasks
yatinmaan pushed a commit that referenced this issue May 8, 2023
* feat: Add support for HTTP(s) proxy

Signed off: Ivan Vaitusionak

Issue: #608

Attribute: Ivan Vaitusionak
carlocorradini pushed a commit to carlocorradini/rumqtt that referenced this issue Aug 3, 2023
* feat: Add support for HTTP(s) proxy

Signed off: Ivan Vaitusionak

Issue: bytebeamio#608

Attribute: Ivan Vaitusionak
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Not moving forward; blocked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant