
21 Feb
2005
21 Feb
'05
5:43 a.m.
John Goerzen wrote:
It turns out that Network.Socket.recv raises an EOF error when it gets back 0 bytes of data.
As it should... recv(2) returns zero bytes precisely when it reaches EOF; this is the standard sockets-API EOF indicator. See any sockets tutorial.
HTTP is expecting it to return an empty list for some reason.
That is odd; HTTP must be broken. --KW 8-)