Re: topological closeness....
"Public cacheing" has little merit, as efficiency of cacheing decreases when covered population grows beyond some threshold (i.e when diversity of requests overwhelms the cacheing capacity -- process better known as "thrashing"). On the other side, small populations do not produce aggregatable demand patterns. I.e. it looks like that ISP-provided cache servers would be optimal. Conviniently, that allows to sidestep the problem of finding cache servers. When you never talk to other provider's cacheing servers you don't need to locate them. There are two ways to do distribute load: "supply side" caches (like secondary DNS servers) and "demand side" caches (like cacheing proxy servers). The supply-side cacheing has a fundamental problem is that you cannot tell which supply-side server is best. So much is clear from the DNS saga. --vadim
On Mon, 13 May 1996, Vadim Antonov wrote:
"Public cacheing" has little merit, as efficiency of cacheing decreases when covered population grows beyond some threshold (i.e when diversity of requests overwhelms the cacheing capacity -- process better known as "thrashing").
On the other side, small populations do not produce aggregatable demand patterns.
I.e. it looks like that ISP-provided cache servers would be optimal.
Especially so since ISP's have the opportunity to do social engineering on their users by maintaining a "What's HOT" page on their server with daily updates. If you can get people to check in on your WWW reviews first then you have a much greater chance of getting cache hits. Michael Dillon Voice: +1-604-546-8022 Memra Software Inc. Fax: +1-604-546-3049 http://www.memra.com E-mail: michael@memra.com
participants (2)
-
avg＠postman.ncube.com -
Michael Dillon