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.

Sign up for GitHub

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

Jump to bottom

What is the purpose of drive()? #53

Closed
andrewbanchich opened this issue Sep 4, 2020 · 2 comments
Closed

What is the purpose of drive()? #53

andrewbanchich opened this issue Sep 4, 2020 · 2 comments

Comments

@andrewbanchich
Copy link

I'm confused about why this is necessary. Shouldn't whatever runtime you're using poll the Future to completion just like any other Future?
@inejge
Copy link
Owner

inejge commented Sep 5, 2020

Since LDAP is a multiplexed protocol, I saw the separation of the connection (LdapConnAsync) and the handles (Ldap) as the most straightforward implementation strategy. Making the separation visible and explicit ought to make managing the connection lifecycle more flexible, without being too much of an ergonomic burden.

@andrewbanchich
Copy link
Author

Okay, thanks for clarifying!

@mdecimus mdecimus mentioned this issue May 29, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@inejge @andrewbanchich