Re: [weirds] feedback on draft-designteam-weirds-using-http

Andy Newton <andy@arin.net> Thu, 17 May 2012 20:10 UTC

Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E54821F8686 for <weirds@ietfa.amsl.com>; Thu, 17 May 2012 13:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uhzl22ynFYkG for <weirds@ietfa.amsl.com>; Thu, 17 May 2012 13:10:41 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id E58C721F85D5 for <weirds@ietf.org>; Thu, 17 May 2012 13:10:40 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 8F0AF213685; Thu, 17 May 2012 16:10:40 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 1025D213631; Thu, 17 May 2012 16:10:40 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Thu, 17 May 2012 16:10:06 -0400
Received: from CHAXCH02.corp.arin.net ([169.254.2.4]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0247.003; Thu, 17 May 2012 16:10:21 -0400
From: Andy Newton <andy@arin.net>
To: Julian Reschke <julian.reschke@gmx.de>
Thread-Topic: [weirds] feedback on draft-designteam-weirds-using-http
Thread-Index: AQHNMqKPZqJhq//TLk+q9jbSHfxA95bOVqoAgAATlgCAABmyAIAAAfuAgAAVxQCAAAoqgIAAChcA
Date: Thu, 17 May 2012 20:10:20 +0000
Message-ID: <17AD5E3E-8933-4E1A-9618-B174FC2C9F41@arin.net>
References: <20120517173250.5000.qmail@joyce.lan> <4FB537EB.7010908@gmx.de> <309CE4E2-5A61-40EB-8B0C-A979B3F15D26@arin.net> <4FB552B5.40900@gmx.de>
In-Reply-To: <4FB552B5.40900@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <BD818717DAA3DE4C9AB71379A16399BC@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@iecc.com>, "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] feedback on draft-designteam-weirds-using-http
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 20:10:42 -0000

On May 17, 2012, at 3:34 PM, Julian Reschke wrote:

> On 2012-05-17 20:57, Andy Newton wrote:
>> 
>> On May 17, 2012, at 1:39 PM, Julian Reschke wrote:
>> 
>>> On 2012-05-17 19:32, John Levine wrote:
>>>>> Using URI templates sound promising.
>>>> 
>>>> I sure hope not.  URI templates are a reasonable way to try to put a
>>>> consistent layer on top of a bunch of existing inconsistent http
>>>> services.  But in this situation, where we're able to spec the URIs
>>>> from scratch, they're just an extra level of unneeded complexity and
>>>> cruft.
>>>> 
>>>> R's,
>>>> John
>>> 
>>> I have no problem with the protocol hardwiring things into URIs, if that can be done. But please stay away from the term "restful" then.
>> 
>> Can you elaborate on this? Are you making a REST purity argument? I'm confused.
>> Sorry to be thick headed here.
> 
> If you hard-wire the URI format, and there's no discovery whatsoever, you don't take advantage of <http://en.wikipedia.org/wiki/HATEOAS>.
> 
> Now my experience is that most of the time, discussions about whether something is "restful" aren't productive. It's not essential that everything is "restful". What's essential is that it works.
> 
> That's why I initially said that you should stay away from the term unless you really plan to fully embrace it :-).

We are using the term RESTful and not REST, which is generally interpreted as borrowing from REST but not being totally compliant to the principles.

-andy