> > So if tpserver-cpp misses an update for whatever reason, it will mean 12
> > minutes between updates, so it will be deleted anyway. To avoid that
> > fate on a coforming server you need to update less then 5 minutes, which
> > is not allowed.
>
> No, you need to update less then 5 minutes *when you are successful*. If
> you weren't able to register then you can update as often as you want.
s/you need to/you may not/
A compliant server may update once every 10 minutes. So this client
will be removed from the metaserver 50% of the time, network and timer
jitter guarantees the delta between the updates will never always be
exactly at 10min or less. This means a compliant metaserver will not
reliably show compliant clients.
If you prefer, view it as a case of Shannon - you need to measure at 2x
frequency of the signal. So if the update is every 10min, then you need
to kick old servers off every 20 minutes.
> The metaserver will only ban you if it gets an update less then x
> minutes between.
>
> If you are having network problems which are causing you to drop - maybe
> you shouldn't be on the metaserver anyway?
That works both ways.
However by making the server complain about not connecting to the
metaserver, it is essentially saying all servers should be connecting to
the metaserver...
> > > I agree with you though.
> >
> > ;-)
>
> > > > That way servers can run at the minimum frequency and not be deleted
> > > > everytime there is network jitter. Also allows a client running at < 10
> > > > minutes to survive a transitory failure easier.
>
> A transitory failure should be noticed by the server.
This is exactly my point.
> Anyway - if it
> disappears when a failure occurs isn't this the correct action?
Yes, but 'failure' is not missing a single update over a HTTP
connection.
nash
[Wondering why s/1/2/ is so hard in this case]
_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
