IETF Logo Mail Archive

Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ....

Bill Roome <w.roome@alcatel-lucent.com> Thu, 28 July 2011 16:33 UTC

Return-Path: <w.roome@alcatel-lucent.com>
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 11E3121F8C10 for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 09:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 BPdBHNQRakQy for <alto@ietfa.amsl.com>; Thu, 28 Jul 2011 09:33:15 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 02EA121F8B1A for <alto@ietf.org>; Thu, 28 Jul 2011 09:33:14 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p6SGXCqJ028710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2011 11:33:12 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p6SGXBGe007405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 Jul 2011 11:33:12 -0500
Received: from [135.104.34.106] (wdr-i7mbp.research.bell-labs.com [135.104.34.106]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p6SGXAIq020666; Thu, 28 Jul 2011 11:33:11 -0500 (CDT)
User-Agent: Microsoft-MacOutlook/14.12.0.110505
Date: Thu, 28 Jul 2011 12:33:10 -0400
From: Bill Roome <w.roome@alcatel-lucent.com>
To: "Thomson, Martin" <Martin.Thomson@commscope.com>, "alto@ietf.org" <alto@ietf.org>
Message-ID: <CA570735.63C8%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ....
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F040D2C3923@SISPE7MB1.commscope.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ....
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 16:33:16 -0000

I would appreciate it if you could explain how my proposal increases the
coupling between the client and the server.

	- Bill

On 07/28/2011 11:09, "Thomson, Martin" <Martin.Thomson@commscope.com>
wrote:

>The idea that you propose - and your philosophy - violates one of the
>core tenets of RESTful design by increasing the coupling between client
>and server.
>

v2.23.0 | Report a Bug | By Email