Re: tasksing and TCP sockets

[Dave Thompson <david.thompson1@worldnet.att.net>]

On Tue, 31 Jan 2006 00:59:45 -0600, tmoran@acm.org wrote:

> >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".

In Windows-the-GUI, or at least for a GUI task/thread on Windows.

But for Windows-the-OS (a non-GUI task/thread or "console" program)
plain old recv() and if you wish select() work just fine.

<snip>

<OFFTOPIC> I feel impelled to re-quote this prior line:

>   TCP server that simulates the world

I realize it makes sense in the context of the OP system description,
but just looking at it in isolation reminded me all too forcefully of
any number of past project breakdown/deliverable items with
demure-looking descriptions that turned out to be disasters. <G?> </>

- David.Thompson1 at worldnet.att.net