Vanilla Netrek Server Development Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[VANILLA-L:966] Re: Metaserver Replication
> Okay, in summary we have the following situation;
>
> 1) the metaserver.us.netrek.org has apparently disappeared, people are
> yelling, and we can't find Nick,
Actually, because metaserver.netrek.org and metaserver.us.netrek.org are
both the same, they are both down. The default metaserver in the client
is metaserver.netrek.org (and it should remain that way).
> 3) metaserver.us.netrek.org will be pointed at Bob's server once it is
> up.
I will point metaserver.netrek.org at both Bob's and Carlos' server
(2 A RRs).
> I support the following future plans;
> a) run with three or more metaservers,
> b) produce a COW patch that will fallback to another metaserver on
> failure to connect,
That's the important part.
> c) continue to use just ONE metaserver for key distribution,
Nod.
> d) produce a VANILLA patch that will provide a server-list only
> metaserver that can be enabled as a function of newstartd, such that
> servers can provide backup for the metaservers.
> I do NOT support re-coding of the metaserver. The current code is
> simple, available, works well, and is quite compatible with the existing
> client and server code base. Re-coding it would be a large effort due
> to interoperability testing, and could significantly impact the
> credibility of the metaserver effort.
The client patch should get all A-Records for metaserver.netrek.org and
try them one at a time.
Cheers,
-Sven
+
++ Vanilla-l Mailing List ++
To unsubscribe: send "unsubscribe vanilla-l" to majordomo@real-time.com
For more information: http://archives.real-time.com
References: