Skip to content

Conversation

@SabrinaJewson
Copy link
Contributor

Motivation

The current .close() method is mostly useless, because it does not allow sending a close frame and takes ownership of the WebSocket, which even forbids implementing the normal WebSocket close handshake.

Solution

Remove .close(), and document the behaviour of WebSocket close handshakes.

Closes: #2964

Copy link
Member

@jplatte jplatte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Got a few questions / suggestions about the new docs.

@jplatte jplatte enabled auto-merge (squash) October 11, 2024 08:56
@SabrinaJewson
Copy link
Contributor Author

Ah. I capitalied “axum” based on other examples in the repo of it beïng capitalized. They should probably be removed, I guess.

@jplatte jplatte merged commit c6e6b4e into tokio-rs:main Oct 11, 2024
18 checks passed
@jplatte
Copy link
Member

jplatte commented Oct 11, 2024

Yeah, it should. In the readme it's consistently lowercase.

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.

Expose Websocket close frame when closing from server side

2 participants