Re: Design question
- From: "Vadym Stetsyak" <vadym_s@xxxxxxx>
- Date: Thu, 19 Jan 2006 19:49:11 +0200
IMO the good approach is to inroduce server, in which clients will
"register" or connect.
Server will have the list of connections ( machines table ).
Then you send data to the server, and server routes it to the clients that
are present in the connection list.
If you want design a failover mechanism then 1 server will be not enough.
--
Vadym Stetsyak aka Vadmyst
http://vadmyst.blogspot.com
"Droopy" <droopytoonnospam@xxxxxxxxxxx> wrote in message
news:Xns9750A7284FBF4droopytoonnospamhotm@xxxxxxxxxxxxxxxxx
> 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.
.
- Follow-Ups:
- Re: Design question
- From: Droopy
- Re: Design question
- References:
- Design question
- From: Droopy
- Design question
- Prev by Date: Re: Design question
- Next by Date: Re: Best approach?
- Previous by thread: Re: Design question
- Next by thread: Re: Design question
- Index(es):
Relevant Pages
|