Very Computer

1. Receiving TCP ignores sending data when receiving buffer is full???

I have an application where a server sends data on either a signal
interrupt (A) or an alarm (B) on the same non-blocking stream socket.
So A & B continously send data over the socket.  Occasionally a
problem occurs when the sequence is like this: A sends, B sends but
the receiving socket only got data from A and not B. In Richard
Stevens's Unix Network Programming Vol1 he indicated the following:

      "With TCP the available room in the socket receive buffer is the
window that TCP advertises to the other end.  The socket receive
buffer can not overflow because the peer isn't allowed to send data
beyond the advertised window.  This is TCP flow control and if the
peer ignores the advertised window and sends data beyond the window,
the receiving TCP discards it".

   Is this what happened in my case?  If so is there a way for the
sending process to check the advertised window before sending to make
sure the sending data won't be discarded?  If not is there a solution
to make sure the receiving TCP won't discard the data?  Since data
from B is more important than data from A is there a way to flush the
receiving buffer before sending data from B to make sure the receiving
buffer will get the data from B?

 Any help is much appreciated.  Thanks in advance.

2. scsi errors on debian linux 2.2.20-pmac on Unax C600

3. TCP send & Receive Buffer limit

4. Real newbie basic X question - Red Hat 5.2

5. Red Hat - How do I figure out and change TCP send/receive buffers?

6. What's the mechanism of hardware driver in linux?

7. Setting TCP receive buffer default size on Solaris 2.4

8. Konqueror crash with KDE 2.2

9. TCP Ques - How to find actual bytes in the TCP send buffer And Connection Que length

10. Sending and receiving at the same time (send & recv)

11. change Send-/Receive-buffer size? (like in WIN95)

12. Freebsd 4.3 adjust receive/send buffer size how?

13. Why do I receive EWOULDBLOCK on send() besides (the buffer is full)?