-
Notifications
You must be signed in to change notification settings - Fork 998
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
feat(swarm): keep Connections on the same Task #2536
feat(swarm): keep Connections on the same Task #2536
Conversation
We know upgrade a PendingConnection on the same Task, instead of moving it back to the main Task, and spawning another one
1c783c2
to
88cc599
Compare
Thanks @dignifiedquire ! Do you mind adding some rationale on why this is better? :) Is it supposedly easier to understand? Less susceptible to certain error conditions? Better encapsulation? |
The idea of doing this, arose from me working on trying to integrate rust-libp2p with https://github.com/DataDog/glommio/. With that executor, connections are not necessarily |
Thanks for that! I'll have a look with that in mind later :) |
I think in principle, I am okay with this direction.
Does this mean, only the final connection is |
This pull request has merge conflicts. Could you please resolve them @dignifiedquire? 🙏 |
This pull request has merge conflicts. Could you please resolve them @dignifiedquire? 🙏 |
I guess we can close this as stale. |
We now upgrade a PendingConnection on the same Task, instead of moving it back to the
main Task, and spawning another one.
@mxinden this is a first pass at what we talked about, in regards to keeping the connection on a single task once established.
Depends on #2535