Re: tasksing and TCP sockets

[tmoran@acm.org]

>You should _not_ need delay statements. Redesign to be waiting on
>socket completions.
  If the allowed response latency isn't terribly short (and it doesn't
sound like it is here) there's nothing wrong with letting the system
buffer up input while the reading task does a delay.  Just use a blocking
socket and poll to see if there's more input data available.  Remember
that "waiting on socket completions" in Windows means "polling the Windows
message loop for a socket completion message".
  But it seems to me that if the object is to use TCP to emulate hardware,
one should design for that hardware and do whatever is needed with UDP or
TCP to make the best emulation.  Is the intended hardware going to be
polled or generate interrupts or Windows messages or what?