sockets - Continue to use the same connection after receiving [FIN, ACK] -


i see servers stop connection once single request done sending [fin, ack]

from wiki,

a connection can "half-open", in case 1 side has terminated end, other has not. side has terminated can no longer send data connection, other side can. terminating side should continue reading data until other side terminates well.

in case want speed requests avoiding repeating handshake per request. possible client keep communicating server terminated end? there response server or server read request without responding?

usually, when terminate write half of tcp connection, means you're done communicating , wait partner (whether it's server, client or equal counterpart) finish it's transmissions. when partner ready, terminates write half , tcp connection closed.

so if server has terminated end, you're still able send data reliably, aren't able receive result.

if don't want handshakes in tcp, why not taking protocol without handshakes? example udp, if messages aren't heavy , intense.


Comments

Popular posts from this blog

SVG stroke-linecap doesn't work for circles in Firefox? -

routes - Laravel 4 Wildcard Routing to Different Controllers -

cross browser - XSLT namespace-alias Not Working in Firefox or Chrome -