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

>Einar,
>
>Not really. That's just how I read your original post. If the commands aren't really a single session, so to speak, then opening and closing the port for each command would indeed seem more logical and clean. It then becomes 250 sessions (or transactions) per cycle (or session ... or whatever verbage you want to use). Either direction you go won't matter too much I suspect, but the main thing would be code readability and maintainability so you may want to look at it from that angle instead.
>
>HTH,
>Chad
>
>
>>Chad,
>>I guess you could look at the 250 commands as one session, but I have never thought of it as one session because the commands are not related to eachother.
>>
>>
>>Can you see any other advantages of considdering the 250 commands one session other than overhead and a slight performance in time?
>>
>>Einar