Re: [alto] Caching ALTO
Robert Varga <robert.varga@pantheon.sk> Thu, 28 July 2011 17:56 UTC
Return-Path: <robert.varga@pantheon.sk>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3335511E80CC for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 10:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level:
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aW8yQSSrV500 for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 10:56:35 -0700 (PDT)
Received: from amalka.pantheon.sk (amalka.pantheon.sk [81.89.59.174]) by ietfa.amsl.com (Postfix) with ESMTP id 9379511E80C9 for <alto@ietf.org>; Thu, 28 Jul 2011 10:56:35 -0700 (PDT)
Received: from [10.0.2.15] (natint3.juniper.net [66.129.224.36]) by amalka.pantheon.sk (Postfix) with ESMTPSA id D97B1208C1 for <alto@ietf.org>; Thu, 28 Jul 2011 19:57:36 +0200 (CEST)
Message-ID: <4E31A2D0.9050003@pantheon.sk>
Date: Thu, 28 Jul 2011 10:56:32 -0700
From: Robert Varga <robert.varga@pantheon.sk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: alto@ietf.org
References: <8B0A9FCBB9832F43971E38010638454F040D2C3928@SISPE7MB1.commscope.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F040D2C3928@SISPE7MB1.commscope.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [alto] Caching ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 17:56:36 -0000
Thanks for bringing this up, as it slipped my mind. Maybe we could design a few optional test cases to catch this at the next interop? Bye, Robert On 07/28/11 10:35, Thomson, Martin wrote: > One of the concerns that I had from my brief look at the server implementations on offer the other night was the lack of support for caching mechanisms. > > Thinking about Robert's request for example scenarios, it seems sensible that EVERY alto flow starts with a request to the IRD. That is, the application always retrieves it, but it is probably cached locally. > > Caching is going to be key to the scalable performance of this protocol. Implementing that caching in clients is a reasonable starting point, but what I'm seeing right now is that clients are caching on their own. There is no guidance being given by servers. > > Doing this means that you can't take advantage of the existing caching infrastructure of the web. > > It's really quite easy. All you need to do is provide Cache-Control headers. > > --Martin > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto
- Re: [alto] Caching ALTO Vijay K. Gurbani
- [alto] Caching ALTO Thomson, Martin
- Re: [alto] Caching ALTO Richard Alimi
- Re: [alto] Caching ALTO Robert Varga
- Re: [alto] Caching ALTO Picconi Fabio