-
Notifications
You must be signed in to change notification settings - Fork 630
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
Question: Half Closed Connections #35
Comments
We should be able to do that indeed - that seems in fact a miss from TCP client and even Http client depending on it! |
Thanks guys for the REACTIVE response :-) |
Like in reactor-core the ideal goal is to bring a patch every month or so. I'd expect a new version in March for instance before Spring 5 RC1 possibly. |
Hi, |
@Fetsivalen Did you try the latest release? |
@Melozzola @Fetsivalen tested this with the latest 0.9.x and it is working |
@violetagg I missed that option. Thanks, i't looks like it will cover my case. |
I'm wondering if there is a way in reactor-netty to shut down the output (from the client to the server) once the data has been written to the channel. Shutting down the output means calling SocketChannel#shutdownOutput()
Essentially I have a Publisher that is producing the data to send. Shutting down the output when the Publisher finishes might be too early because there might be pending writes. Is there a way to intercept when all the writes have been completed?
My TCP server (on which I don't have control) is waiting for the shut shutdownOutput() signal before starting sending the response.
The text was updated successfully, but these errors were encountered: