std.socket - problems closing socket

[Regan Heath]

On Mon, 03 Oct 2011 19:41:14 +0100, simendsjo <simendsjo at gmail.com> wrote:
> It seems nginx is to blame here, and not me. I tried Lighttp and it  
> works. It gives several EWOULDBLOCK, but I can just handle these again  
> with no problem. I should have tried this sooner... I've used a lot of  
> time trying to track down these problems :|

EWOULDBLOCK is to be expected, it simply means you've tried to read when  
there is no data available, before the close/shutdown(SEND) from the other  
end. :)

-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/