I don't mind longish names if they are actually descriptive and useful. I really don't like names (short or long) that serve to obfuscate the code. Just because the code works, it doesn't mean that it is good code.

You're closer with Socket.Select rather than the others which work on WaitHandles. I'll look into getting a WaitHandle-based object associated with a socket so I could use the regular WaitForMultipleObjects but the client's happy with the socket-workaround I told in last mail. Thanks again. K

Hi, sorry for not replying earlier - this is perfect, thanks. I know, pretty obvious - just wasn't spotting it or searching with the correct terms. Cheers, Kev