Hidden buffer in TCPsocket?

I’m very confused:

In my simple test, packets sent over while xojo is “stuck in a loop” are queued at the destination and made available on the next event fire, as expected.

Stacks have an internal queues to cope with this, and they throw errors (like WSAEWOULDBLOCK) when their queue fills if they can’t clear it down quick enough.