Home

 


Re: Client doesn't drop failed source Posted on: Injection- Wed, 20 Jan 2010 08:04:33 +0000 (UTC)

David Mills wrote:
>
> Not true. The dispersion does increase, but the server is valid until
> the dispersion exceeds the select threshold, usually in four or five
> more missed messages.

That's why I said the quality measures are invalidated, rather than the
server is invalidated. I probably should have said "effectively". I
guess that anti-clock hopping may reduce the effect.

I was really trying to correct my initial reading, that the only
reachability check was reachability == 0. There is also a reachability
& 7 == 0 check, earlier in the code, which results in a sample with the
maximum possible dispersion value being loaded.

I can't tell, quickly, what gets loaded when there are only one or two
missed polls. I'd always assumed that the filter slots tracked the
rachability ones, but maybe not.
56525. Re: Client doesn't drop failed source
56526. Re: Client doesn't drop failed source
56527. Re: Client doesn't drop failed source
56528. Re: Client doesn't drop failed source
56529. Re: Client doesn't drop failed source
56530. Re: Client doesn't drop failed source
56531. Re: Client doesn't drop failed source
56532. Re: Client doesn't drop failed source
56533. Re: Client doesn't drop failed source
56534. Re: Client doesn't drop failed source
56535. Re: Client doesn't drop failed source
56536. Re: Client doesn't drop failed source
56537. Re: Client doesn't drop failed source
56538. Re: Client doesn't drop failed source
56539. Re: Client doesn't drop failed source
56540. Re: Client doesn't drop failed source
56541. Re: Client doesn't drop failed source
56542. Re: Client doesn't drop failed source
56543. Re: Client doesn't drop failed source
56544. Re: Client doesn't drop failed source