-
Notifications
You must be signed in to change notification settings - Fork 122
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
Allow SseEventSink.close() to throw IOException #859
Comments
Hi @jimma I think this makes sense. Would you code up a pull request with this change? Please code it against the Thanks! |
I do not have a strong opinion about this, but it would not align with other close methods such as on a |
Anyway, it is a backward-incompatible change, and as such, it should go into a major version, not minor 3.1, imho. |
Agree. |
Is it better allowing SseEventSink.close() to throw IOException, then the underlying IOException doesn't need to be wrapped in RuntimeException to throw up ? The caller can decide what to do when catch this IOException.
The text was updated successfully, but these errors were encountered: