Design question

Hi,

I write a C# application that is "routing" messages (from other C#
applications) to other machines using Sockets.
To route these messages, each machines has to know the existence of all
others.
I need a kind of up-to-date "machines table".
Machines can appear or disappear from that list at any moment.
I want a "simple" way of handling this.
Should I use Tcp, Udp, Win API, Directory service, ... ?
Shoud each machine have its own copy of the machines table or should I use
a server (with automatic failover solution) ?

I am using VS2003 C# on Win XP.

Thanks in advance.
.

Relevant Pages

  • Re: Board fabrication to make custom lamp boards?
    ... lamp boards from under newer WMS machines made, so you can use the twist ... Either for custom machines or to replace earlier machines that have the ... reliable than discrete sockets. ... The hardest part it seems is getting the cutout correct I'd assume they ...
    (rec.games.pinball)
  • Re: Help needed: Wierd Socket/RMI issue
    ... > has opened sockets, accepts them, has the open sockets ... you describe has any effect on remote machines. ... > traffic over the network? ... the socket state is LISTENING. ...
    (comp.lang.java.programmer)
  • Re: Linux Socket Problem?
    ... and for each pair of machines ... > recving msg, the other two for sending and recving acks. ... > signals resp. ... selectshould always be used with non-blocking sockets. ...
    (comp.os.linux.networking)
  • Re: Inter Process Communication, full-duplex
    ... Sockets are fine, if you are trying to communicate between 2 machines, but I do not have that problem. ... the machines that these programs will be running on have a very strict firewall policy. ...
    (comp.lang.java)
  • Linux Socket Problem?
    ... and for each pair of machines ... Only the socket for recving msg is set to be asynchronous ... Linux sockets causing this problem? ... from my above email addr. ...
    (comp.os.linux.networking)
Loading