🚀 go-pugleaf

I have a current thread going on Blocking Client Sockets but I also have a
problem with the Client Socket Read Event so I started this thread as well.

My problem is that the Read Event on a non Blocking Client Socket is not
firing all the time, that is a data is received on the socket but the event
does not fire. Now I have been using the application on many machines and
have not seen this until the application was placed on a very fast network
using Gigabyte network cards and running fast machines using windows XP.

So what happens is I may get the event firing for a bit then it stops
firing. I can see the messages coming into the machine through a TCP sniffer
but my application does not get the read event. If I close the socket and
reopen it then it works for a bit and then stops again. I know the socket is
still connected because I can send a message from the client to the server
and every message is received.

So can anyone help me in determining why the read event does not fire, or
explain to me when the read event should fire. I really do need some help in
this as my application is failing because I can't see the data coming from
the server.

Thanks

Mike