Re: [p2pi] Charter and problem statement
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2pi] Charter and problem statement
Actually, caches will probably want to be included in all ALTO responses so that they are contacted by peers, so that they can determine whether they want to cache the content (and have a data source for the cache if so).
- Laird Popkin, CTO, Pando Networks
mobile: 646/465-0570
----- Original Message -----
From: "Enrico Marocco" <enrico.marocco at telecomitalia.it>
To: "Sebastian Kiesel" <sebastian.kiesel at nw.neclab.eu>
Cc: "Laird Popkin" <laird at pando.com>, p2pi at ietf.org
Sent: Tuesday, July 15, 2008 9:32:18 AM (GMT-0500) America/New_York
Subject: Re: [p2pi] Charter and problem statement
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
_______________________________________________
p2pi mailing list
p2pi at ietf.org
https://www.ietf.org/mailman/listinfo/p2pi
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.