Theodore Hong writes:
Bill Trost <trost at cloud.rain.com> wrote:
> Theodore Hong writes:
> When an item is inserted, it gets an automatic one
> hit.
>
> That would mean that a newly-inserted item could get bumped
> off the queue by the next DataSend.
I`m not quite sure what you`re objecting to. Is it the
one-hit- after-insert? It`s true that a new insert could bump
off a slightly-less new insert. But if we don`t do that, and
the store is full, new items will never be able to get in the
queue at all! (They will join at the back, then the queue
will be culled, and they`ll immediately be dropped.)
Yes, zero hits is worse than one hit, but one hit is still pretty bad.
Given the choice between what you describe and the current behavior, I'd
stick with the current behavior.
Inserts should go neither at the top nor the bottom, but probably
near the middle. Their popularity is unknown when the data is first
received, so there is little reason to bias their queue position either
way. Not to hot, not too cold, but juuust right...
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
