🚀 go-pugleaf

"SF" <invalid@NOSPAMinvalid.com> wrote in message
news:44ce1ea3@newsgroups.borland.com...

> what happens if a connected socket (client or server, blocking or
> non-blocking doesn't matter) receives a lot of data, but the
> application doesn't read it (or it's not fast enough)?

The unread data remains in the receiving socket's internal buffer.
Eventually, the buffer will fill up.  Once the buffer cannot accept any
further data, the sending side will do one of the following:

1) if the sending socket is non-blocking, then any writing will fail with an
WSAEWOULDBLOCK error until the receiving buffer has been cleared.  At which
time the sender will receive a FD_WRITE notification indicating that the
socket can be written to again.  In the meantime, any outbound data that
returned a WSAEWOULDBLOCK error would have to be cached so that it can be
sent at a later time so that it is not lost.

2) if the sending socket is blocking, then any writing will simply block
until the receiving buffer is cleared.  Unless there is a writing timeout
applied to the socket, in which case the writing will fail if the timeout
elapses.

> Is it like a serial port that after a while there's a buffer
> overflow (with loss of data)?

No.


Gambit