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

No shutdown raw stream #102

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

No shutdown raw stream #102

wants to merge 1 commit into from

Conversation

quininer
Copy link
Member

Close #64

@quininer quininer force-pushed the quininer/no-shutdown branch from 28eaa4d to efa87f5 Compare February 11, 2025 15:05
@quininer quininer requested a review from djc February 12, 2025 04:19
@djc
Copy link
Member

djc commented Feb 12, 2025

Can you extend the PR description with some context? Why is this the best path forward?

@quininer
Copy link
Member Author

I mentioned it here. if there is a consensus, I will add more information in comments later.

@djc
Copy link
Member

djc commented Feb 18, 2025

It seems surprising to not shutdown the TCP socket if shutdown() is called on the containing TlsStream -- I think it would help to gather up all the context/reasoning in one place (in this PR).

@ctz
Copy link
Member

ctz commented Feb 18, 2025

I think the most sensible default is to shutdown the TLS and TCP connections. Perhaps we could have an explicit and #[must_use]-marked function that shuts down the TLS side, and yields the IO for people who have a further use for it?

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.

Remove TCP shutdown
3 participants