Einar,

Nope. ;) The closest thing I've done would probably have been dealing with sockets and socket servers broadcasting messages in a multi-threaded environment. And that was in Java (pre-.NET days). Think of a serverless peer-to-peer messaging system something like ICQ but without a server. You could see a list of all clients online and send messages to either individuals or everyone. There was a socket server running on one thread and it would kick off a new thread for every message received. The main thread was for the UI and sending messages.

HTH,
Chad


>Chad,
>Yes like someone else said it will make the code cleaner and easier to maintain if I stick with the single transaction per cycle. In most installations there will not be 250 transactions per cycle, it will be closer to 40-75 transactions per cycle (250 is the maximum limit per cycle).
>
>Have you done some programming in .NET which includes connecting, sending, receiving, disconnecting over the TCP protocol?
>
>Einar