![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Sebastian Kiesel wrote: > On Fri, Jul 11, 2008 at 11:10:41AM -0400, Laird Popkin wrote: >> For this level of discussion, I agree that caches should simply be >> viewed as a peer in ALTO. > > What happens if we consider caches and rare content, i.e., content where > the likelyhood is high, that there is a cache miss when we ask for it > and that the cache will never deliver a second copy of it? It might not > be wise to select a cache which is in the "opposite direction" of the > original content, even if connectivity to the cache is "better" > (according to whatever criteria). If the cache tries to fetch the > content the request may pass by the client and go through the same "bad" > link plus twice through the "good" one. As long as caches are viewed as regular peers, they will be included in ALTO requests/responses only if they actually have the resource the querying peer wants to access. -- Ciao, Enrico
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ p2pi mailing list p2pi at ietf.org https://www.ietf.org/mailman/listinfo/p2pi