You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2018. It is now read-only.
It seems that return Box::new(future::done(Ok(req))) doesn't close the connection.
My client side:
let mut socket = TcpStream::connect(addr).unwrap();
socket.write(msg.as_bytes());
let mut result = String::new();
println!("waitiing for server to return");
let response = socket.read_to_string(&mut result);
info!("the server return: {}", result);
will block at socket.read_to_string()
The text was updated successfully, but these errors were encountered:
Not really. I read data to buf with a fixed len, print it, then eixit the client process.(I don't care what server returns in that app).
I don't understand what alexcricht said. We can not close connection at server side?
Should I close this issue?
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
It seems that return Box::new(future::done(Ok(req))) doesn't close the connection.
My client side:
will block at socket.read_to_string()
The text was updated successfully, but these errors were encountered: