Vanilla Netrek Server Development Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[VANILLA-L:987] Re: [VANILLA-L:985] Re: [VANILLA-L:984] Re: [VANILLA-L:983] Re: metaserver is reborn
> Carlos Y. Villalpando wrote:
> > And don't use metaserver.netrek.org for solicitation unless the
> > solicitation code is changed to go through all the IPs returned.
> Not so. Just add the servers one at a time to the .metaservers file,
> and set update timers as appropriate for your situation.
That's what I was trying to tell them what to do.
metaserver.netrek.org returns the IP's of BOTH metaserver.us and
metaserver2.us in round-robin order. If they just use
metaserver.netrek.org, they will do one of two things: (not being
familiar with the code)
1) If the solicitation code does a DNS lookup each time, the will hit
each one of the metaservers at 1/2 the rate defined in their timeouts.
2) If the only do 1 DNS lookup and store the address. They only talk
to the particular metaserver they happened to get the IP of first.
That being said, I need to go look at that solicitation code.
--Carlos V.
+
++ Vanilla-l Mailing List ++
To unsubscribe: send "unsubscribe vanilla-l" to majordomo@real-time.com
For more information: http://archives.real-time.com
Follow-Ups:
References: