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

Provide custom exceptions about reason of closing connections instead of transport agnostic #148

Open
whyoleg opened this issue Apr 14, 2021 · 0 comments
Open

Provide custom exceptions about reason of closing connections instead of transport agnostic #148

whyoleg opened this issue Apr 14, 2021 · 0 comments
Milestone
0.20.x

Comments

@whyoleg
Copy link
Member

whyoleg commented Apr 14, 2021

ClosedReceiveChannelException is produced by transport specifics - both in TCP and WS implementations.
Looks like it will be better to provide some custom exception for case of failed connection.

Originally posted by @whyoleg in #145 (comment)
@LittleTrickster LittleTrickster mentioned this issue Jul 21, 2021
Open
@ghost ghost mentioned this issue Apr 26, 2022
Open
@whyoleg whyoleg modified the milestones: 1.0.0, 0.16.0, 0.17.0 Oct 5, 2022
@whyoleg whyoleg modified the milestone: 0.16.0 - Transport API/Internals rework, QUIC, Netty Nov 24, 2022
@whyoleg whyoleg removed this from the 0.16.0 - Transport API/Internals rework, QUIC, Netty milestone May 3, 2023
@whyoleg whyoleg added this to the 0.20.x milestone Mar 10, 2025
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
0.20.x
Development

No branches or pull requests
1 participant
@whyoleg