Hopefully the protocol-related talk will be recovered from the old forum
as I also made calculations regarding the poor scalability of the Bloom
filters. The extension was tested in a few hubs several years ago and it
caused complaints from the users which in my opinion can't be solved
with the cur
One practical solution to this is to cache the SF value after share
refreshes and provide that cached value once, when the getter called
from the next ADC info sending. This may need a special getter for this
purpose.
Since we always send an INF right after share refreshes and already got
a nice r
2 matches
Mail list logo