"It depends". It depends on your requirements for what would be a good
choice for sending messages.
I have a solution that has many distributed client applications and one
central server. In my scenario I need to have messages routed from one
client to another and I need to make sure that the messages arrive. To
accomplish that I use MSMQ. It is quite trivial and has more than
adaquate performance for what I need. The solution works by each
client registering themselves with the server via a well known private
queue name. When the server needs to communicate to a client it looks
up its computer name and sends a message to the client on a well know
client queue name.
There are more choices but you would be well served to identify more of
your requirements.
Steve
unwantedspam wrote:
Thank you in advance for reading this.
I need to have two applications send messages over the network to each
other. Basically one server application and (possibly) many client
applications. I am using VS 2003. What choices do I have when it comes
to implementing this. I am currently using (and it is working) the
TcpClient but would like to know what other choices are out there.
Thanks again!