Re: flush buffer using socket recv() with non-blocking flag

Scott,
It should always be a one to one relationship between the send and recv.  My
application sends one command and will recv one respond back from the
server.  Yes, in theory, I could send all three commands and then recv all
three responds back at once.  But this senario will not happen in this
application.

The server is actually not a true socket server application.  It is actually
a modem (v.35) type application.  The network guy puts a CISCO route, that
speak TCP/IP, in between my socket app and the actual modem server.  So, my
app actually speck to this CISCO route and it then sends the data to the
target server.  Sometime if the CISCO route is not configured correctly,
I'll see the respond being echo back to me (seeing the same respond twice).
So, I'm kind of worry that this echoing problem might throw my app to become
out of sync on this one to one send and recv relationship.