Ralith
commented
1 year ago How do I know if my packet has arrived safely?
This depends on what exactly "arrived safely" means to you. Usually what people mean is "has been processed by the remote application", but SendStream::finish only tells you when a stream has been received by the transport -- the application might still shut down or crash or lose power before processing the stream. To be certain that a message was actually processed, you usually need to have an application-layer response of some kind that the peer only sends when it's done.
But it seemed take too long, sometimes over 3 seconds!
Why is 3 seconds too long? If the link is very slow and/or lossy, that might be a perfectly reasonable duration, especially if you're sending much data.
what's the best way for me to detect of there's a connection problem?
Set TransportConfig::max_idle_timeout according to your needs. Also consider setting TransportConfig::keep_alive_interval. Ultimately it's up to you to define what behavior counts as a broken link.
too slow can also be called broken
You'll need to track this yourself, though Connection::stats might be useful.
szguoxz
djc
I have a very basic question, as I am kind of new to this.
How do I know if my packet has arrived safely?
I know I can use sendstream.finish to detect whether it's acked. But it seemed take too long, sometimes over 3 seconds!
Before I know for sure, I don't even know if the line is broken or something.
in a very unreliable environment, what's the best way for me to detect of there's a connection problem? What is the reasonable time and method for me to know: OK, This line is broken (too slow can also be called broken), I got to try something else.