Vanilla Netrek Server Development Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[VANILLA-L:980] Re: [VANILLA-L:978] Re: [VANILLA-L:975] Re: metaserver is reborn
- To: vanilla-l@us.netrek.org
- Subject: [VANILLA-L:980] Re: [VANILLA-L:978] Re: [VANILLA-L:975] Re: metaserver is reborn
- From: "Carlos Y. Villalpando" <unbelver@brain.jpl.nasa.gov>
- Date: Wed, 5 Aug 1998 11:52:04 -0700 (PDT)
- In-Reply-To: <001501bdc09e$d99aab80$4ae167ce@bartig> from "Bill Bartig" at Aug 5, 98 01:28:30 pm
- Reply-To: vanilla-l@us.netrek.org
- Sender: owner-vanilla-l
> >
> >Virtually irrelevant information, unless you happen to be playing from
> >the metaserver machine. Network topologies are way too wacky.
>
>
> Not if the Metaserver does this...
> Takes a "snapshot" of the servers' ping times. Every time the Metaserver
> updates, it could show how many MS + or - the servers ping times have
> changed from the times it recorded previously. That way, if you see a
> server on the list with "+150ms", you will know not to even bother with that
> server
Still irrelevant. You're still only reporting the status of the
metaserver's link. You're link may be rock-solid and it may be the
metaserver that's having problems.
And since there are 3 metaservers, which would you belive if you see
+105 and -105 on two different metaservers?
--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