🚀 go-pugleaf

"Martin" <dev@no.comppromed.spam.com> wrote in message
news:44281b29$1@newsgroups.borland.com...

> The connection that gives me the problem is one that has periods
> where nothing is sent/receive for more than 20 minutes.

Sockets themselves do not have any problems with idle periods.  They don't
care at all whether data is being transmitted frequently or not.  So any
problems you are having are likely caused by problems in your own code that
is managing the sockets.

> The socket is still connected (no disconnect events or errors), but
> later on we find that the other side tried to send something that wasn't
> received by our app.

What does your actual code look like?  Since you are using non-blocking
sockets, my first guess would be that you are not completely clearing the
socket's inbound buffer when data arrives, thus the socket eventually begins
losing notifications when new data arrives.  When data arrives, you have to
read ALL of it at that moment, into your own buffer.  You should not leave
data unread in the socket in between events.


Gambit