Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion How should HATEOAS Links in a json response be handled and why?

Received: by 10.50.33.180 with SMTP id s20mr654405igi.5.1351090473451;
        Wed, 24 Oct 2012 07:54:33 -0700 (PDT)
X-BeenThere: api-craft@googlegroups.com
Received: by 10.50.41.132 with SMTP id f4ls4207992igl.1.gmail; Wed, 24 Oct
 2012 07:54:31 -0700 (PDT)
Received: by 10.43.131.7 with SMTP id ho7mr8586623icc.5.1351090471336;
        Wed, 24 Oct 2012 07:54:31 -0700 (PDT)
Received: by 10.43.131.7 with SMTP id ho7mr8586622icc.5.1351090471327;
        Wed, 24 Oct 2012 07:54:31 -0700 (PDT)
Return-Path: <mikekelly...@gmail.com>
Received: from mail-ob0-f176.google.com (mail-ob0-f176.google.com [209.85.214.176])
        by gmr-mx.google.com with ESMTPS id dx8si386253igc.1.2012.10.24.07.54.31
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 24 Oct 2012 07:54:31 -0700 (PDT)
Received-SPF: pass (google.com: domain of mikekelly...@gmail.com designates 209.85.214.176 as permitted sender) client-ip=209.85.214.176;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mikekelly...@gmail.com designates 209.85.214.176 as permitted sender) smtp.mail=mikekelly...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ob0-f176.google.com with SMTP id x4so598368obh.35
        for <api-craft@googlegroups.com>; Wed, 24 Oct 2012 07:54:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=hd40THb+lnffrDue+vOKAjoPlCw31U8XSUrkEtX/kME=;
        b=lo45r+KXNK3ABKed3yGQ3OTCstc1/aRPI9UtrstDfeHn/M9YBqHOKUJ/yDc1/vjJfu
         WQJfDimw5XxSxUTkuHLN3OxajK2YedZLVR9CPTm8NuKKvw+iphMY231VRRpn6lTqjdak
         FTZEYYMGoQO5eVtFwXt/55q3IGaCtvNvVgRA6sonbNTu+CJkr8OtsIo4LqszFesfC7PV
         HKjEaaqKebKiSI9j77L3r7WlXrxtJoONnP6qkRmRm+c/jUt5ohS2OXPb9FT63MNM5gOa
         j0wQmlZkQtp5QBA88LgCDPgTy5l4U9J60Y4FG+YDdGYy0qXpDvQgcd3UzVrz7rMq36hz
         MSEg==
MIME-Version: 1.0
Received: by 10.60.29.229 with SMTP id n5mr13596946oeh.76.1351090471191; Wed,
 24 Oct 2012 07:54:31 -0700 (PDT)
Received: by 10.60.48.99 with HTTP; Wed, 24 Oct 2012 07:54:31 -0700 (PDT)
In-Reply-To: <CAPW_8m4PcYtJ1nH+PRCYtnKxCF44A9BQhjm8XnpVX=FJGZf...@mail.gmail.com>
References: <e798a1ea-1dc6-4079-af2d-dda8e7f7f3f0@googlegroups.com>
	<f725c08c-f36d-4650-8910-6e3430b361e7@googlegroups.com>
	<7A0172D5-36CB-49D0-9AFE-7887CC642...@gmail.com>
	<CAG=1cLWE_smb6+7BNZta1UsLrQ36-Q53Y2=fHdxu91dZh4-...@mail.gmail.com>
	<CAPW_8m6v9WEdLO-dHOiKPLu5X0iS8CPHQ-eWDSekbFrbrzN...@mail.gmail.com>
	<8AE8BBB9-52A4-442F-ACAB-E7C43BCF7...@gmail.com>
	<CAPW_8m44TDyUKDiErFxVyLitmCfV9H+d5zJh1Z+gBrL=bhV...@mail.gmail.com>
	<CANqiZJaO6sDHz5AwwzvYYFce8nE=CYNiNsk9SA_wxt2ZF88...@mail.gmail.com>
	<CAPW_8m7ZeLDQevqQ5ghcJp+JHjR74TpX_iFvEC-1Niogtpa...@mail.gmail.com>
	<CANqiZJbBtxrLyNs9AeSOYGEpz_Okck6LqnC0kU3O0D3yJfM...@mail.gmail.com>
	<CAPW_8m5mcLwmRqQ50za3Rqn4=cDQ7nx+6z3CcC2N9Y0Z2WK...@mail.gmail.com>
	<CANqiZJaPGg-cLDvoNimApjQcBA7_N_rmWkOa5Dwe67-6voR...@mail.gmail.com>
	<CAPW_8m4PcYtJ1nH+PRCYtnKxCF44A9BQhjm8XnpVX=FJGZf...@mail.gmail.com>
Date: Wed, 24 Oct 2012 15:54:31 +0100
Message-ID: <CANqiZJaO=YU-YAchrrC9qAQXeKHg8cdxUK55hX0Ya_kQtw+...@mail.gmail.com>
Subject: Re: [api-craft] Re: How should HATEOAS Links in a json response be
 handled and why?
From: Mike Kelly <mikekelly...@gmail.com>
To: api-craft@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 24, 2012 at 3:49 PM, mca <m...@amundsen.com> wrote:
> often yes, the list will be a list of at one of the same values (most all my
> designs use rel as a string of space-sep values).

ok so the would work for you?:

_links: {
  self: { href: "foo" },
  queries: [{
    "href": "/foo?first-query"
  },{
    "href": "/foo?second-query
  }]
}