Re: Design question

"Vadym Stetsyak" <vadym_s@xxxxxxx> wrote in
news:ei4lpCSHGHA.3116@xxxxxxxxxxxxxxxxxxxx:

> 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.
>

This is the way I want to do it.
But the "consumers" of my application don't like the server approach for 2
reasons :

1) if only 1 server = single point of failure
2) performance is lower (because message is not sent directly)

Thanks a lot for your answer.
.

Relevant Pages

  • Re: Domain Controller Stops Processing All Login Requests Randomly
    ... > control the clients and shutdown a bunch of machines at once or turn them ... >>> machines simultaneously that are Deep Freeze clients. ... the server exhibited the same behaviour. ...
    (microsoft.public.windows.server.dns)
  • Re: MsgCommunicator v.2.00: Instant Messenger SDK, now with databases support
    ... expect persistent connections. ... they will wait for the server to pick them up. ... your Clients can stay "off-line" for about 30 minutes before they have to ... requests *simultaneously*. ...
    (borland.public.delphi.thirdpartytools.general)
  • sockets, closing and TIME_WAIT
    ... During heavy load the server can't follow anymore because the sockets ... my server should be able to handle 10 clients connecting ... This gets a free position in the array of connections, ...
    (comp.unix.programmer)
  • Re: TCP/IP redundant connections
    ... The clients have persistent TCP connections to the server, ...
    (freebsd-hackers)
  • Re: Intermittent Network Connections
    ... I've just reconnected the Server LAN nic 1 to the ethernet switch (the same ... Server IP config and Client IP config attached. ... > turn is connected to an ADSL modem out to the internet The clients connect to ... >> Clients can sucessfully log in but periodically loose their connections. ...
    (microsoft.public.windows.server.sbs)