gen_tcp:recv - last segement when closed port

Valentin Micic <>
Sun Mar 12 22:02:07 CET 2006

> Anyone who thinks that this procedure might lead to loss of data
> (assuming correctly functioning applications and available network
> connectivity) will have a hard time explaining the initial success of
> the web...

How about this: client opens a connection, issues a request, receives a 
reply and than closes the connection.
To quote from RFC 2616, paragraph

An HTTP/1.1 client MAY expect a connection to remain open, but would decide 
to keep it open based on whether the response from a server contains a 
Connection header with the connection-token *close*. In case the client does 
not want to maintain a connection for more than that request, it SHOULD send 
a Connection header including the connection-token *close*.

See, not that hard at all ;-)


More information about the erlang-questions mailing list