Hi Folks
Im working with my first VB.Net application (I've done some VB6 long time ago), and also my first to use TcpClient. I have the basics down OK so far, but now I need to scale up and have lots of simultaneous connections (~30) to different servers on the same network.
each of the connections will be operating on a different thread from the thread pool and could of course open, close, write, read, etc at any time.
Are there any recommendations or gotchas for when working with multiple simultaneous connections that some of ye with experience in the area could share before I start in? E.g. One of the things I have been thinking about is investigating working directly with sockets rather than the TcpClient, but I dont know if this would bring advantages or not..., or is there some way of having a "collection" of connections like the thread pool collects threads...
Thanks :)
Im working with my first VB.Net application (I've done some VB6 long time ago), and also my first to use TcpClient. I have the basics down OK so far, but now I need to scale up and have lots of simultaneous connections (~30) to different servers on the same network.
each of the connections will be operating on a different thread from the thread pool and could of course open, close, write, read, etc at any time.
Are there any recommendations or gotchas for when working with multiple simultaneous connections that some of ye with experience in the area could share before I start in? E.g. One of the things I have been thinking about is investigating working directly with sockets rather than the TcpClient, but I dont know if this would bring advantages or not..., or is there some way of having a "collection" of connections like the thread pool collects threads...
Thanks :)