Re: Design question

"Vadym Stetsyak" <vadym_s@xxxxxxx> wrote in
news:eOlrOTDIGHA.2012@xxxxxxxxxxxxxxxxxxxx:

>> In fact, the start phase is not that difficult to handle.
>> The problem is that, for now, when a connection between 2 hosts is
>> broken, a message is sent (via TCP connection) to every other hosts
>> connections to keep each hosts table uptodate and an automatic re-
>> connection between these 2 hosts is tried triggered by a timer.
>
> doesn't this introduce inefficiency? You'll get implementation
> complexity, synchronization lag,
> and ineffiecient network usage ( additional network traffic for table
> sync ) for now you have 60 connections on each host, connection is
> broken between 2 of them.
> You have 60 machine tables, which can become desynchronized for
> considerable timeout.
>
> With server-based approach you will have 1 ( several ) machine tables,
> which will be synchronized.
> Consider also traffic through the network, when machines need to
> synchronize machine table.
>
> For failover you can introduce 2 or more servers: primary and
> secondary. Hosts will know about the second one, but will work with
> the 1-st. If primary server is down, they will automatically reconnect
> to the secod one. Primary and secondary servers will have synchronized
> machine table.
>

I agree with you but it is not my design :-(
But now, I am asked to improve/simplify, that's why I am looking for a
better and more simple way to implement this.
I like your "server" approach.
The only thing I have a problem with is the "indirection" imposed by the
server when sending a message.
We send a lot of little messages.

I appreciate your help.
.

Relevant Pages

  • Re: RWW basic question !!
    ... Go to www.internic.net and do a whois lookup of your domain name to see ... Advanced Windows Small Business Server 2003 Best Practices ... determine who hosts your DNS records. ... internet connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 incoming SMTP network level problem
    ... > mail hosts when connected to an ADSL connection. ... > This same server same server receives the SMTP data from all mail ... > It works fine with the cable connection, ... > from ISPs because they tell me there is nothing wrong with my server.) ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange 2003 incoming SMTP network level problem
    ... Done that, on the NIC, the modem and the firewall. ... >> mail hosts when connected to an ADSL connection. ... >> This same server same server receives the SMTP data from all mail ... >> It works fine with the cable connection, ...
    (microsoft.public.exchange.connectivity)
  • Exchange 2003 incoming SMTP network level problem
    ... A new Exchange 2003 server does not receive SMTP data from certain ... mail hosts when connected to an ADSL connection. ... It works fine with the cable connection, ...
    (microsoft.public.exchange.connectivity)
  • HSRP on multilayer switches
    ... Connected to each end of this gigaman are Catalyst ... With the MAN connection, these hosts appear ... The hosts don't run OSPF, though they can run RIPv2 and we could ...
    (comp.dcom.sys.cisco)