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 What are your thoughts on intentionally "breaking the rules" on a collection

Received: by 10.180.98.138 with SMTP id ei10mr332432wib.4.1353002101491;
        Thu, 15 Nov 2012 09:55:01 -0800 (PST)
X-BeenThere: api-craft@googlegroups.com
Received: by 10.180.87.133 with SMTP id ay5ls133091wib.33.canary; Thu, 15 Nov
 2012 09:54:58 -0800 (PST)
Received: by 10.204.10.80 with SMTP id o16mr120079bko.4.1353002098160;
        Thu, 15 Nov 2012 09:54:58 -0800 (PST)
Received: by 10.204.10.80 with SMTP id o16mr120078bko.4.1353002098136;
        Thu, 15 Nov 2012 09:54:58 -0800 (PST)
Return-Path: <dietrich.schul...@googlemail.com>
Received: from mail-bk0-f47.google.com (mail-bk0-f47.google.com [209.85.214.47])
        by gmr-mx.google.com with ESMTPS id t1si1368410bkt.1.2012.11.15.09.54.58
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 15 Nov 2012 09:54:58 -0800 (PST)
Received-SPF: pass (google.com: domain of dietrich.schul...@googlemail.com designates 209.85.214.47 as permitted sender) client-ip=209.85.214.47;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dietrich.schul...@googlemail.com designates 209.85.214.47 as permitted sender) smtp.mail=dietrich.schul...@googlemail.com; dkim=pass header...@gmail.com
Received: by mail-bk0-f47.google.com with SMTP id jk7so853469bkc.20
        for <api-craft@googlegroups.com>; Thu, 15 Nov 2012 09:54:58 -0800 (PST)
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=SyCVKBCz5rpNlrjYIsqH4Gbpfp+gQhEjPcg9DT+LvDY=;
        b=lrpasuVF2QJsBeJurN0OE9ESDMTfg/sn1A7AAuSf4YyPMHSpqfylYq5t1d6qQCeH0f
         Let08ZJlhQYd+SXB4IqR48Z9UPWy5fUxoI5lmVTj+adJwrUXFzWpTfTTPx1oPI/KmSOr
         yOO60DILAu1dvTQeTtNkpFsUwjmVHiLr+toB4OBa+kv95I1olgp8xfW877sIzj3pta7N
         VctTpKNrxCgJszKTtpnJPAUz87RLgDtRCs7ewZZcl1eNe9h4J9M70LQAI7k+BDCdv7QB
         l/tlSZDnrXxsxXXZTHH4n3P1kMItF/Yhd0ghmaHNAkjfvpWAcV6oGJBn795vDVCyzZ3R
         tdVA==
MIME-Version: 1.0
Received: by 10.204.150.213 with SMTP id z21mr807935bkv.45.1353002097966; Thu,
 15 Nov 2012 09:54:57 -0800 (PST)
Received: by 10.204.61.129 with HTTP; Thu, 15 Nov 2012 09:54:57 -0800 (PST)
Received: by 10.204.61.129 with HTTP; Thu, 15 Nov 2012 09:54:57 -0800 (PST)
In-Reply-To: <6ee6abaa-8334-411b-9019-38b77ae225d8@googlegroups.com>
References: <6ee6abaa-8334-411b-9019-38b77ae225d8@googlegroups.com>
Date: Thu, 15 Nov 2012 18:54:57 +0100
Message-ID: <CAC_mumXRHpZQUhCE0Q9N5OycwDZp7ED7E+3cuWYnPb54_Yb...@mail.gmail.com>
Subject: Re: [api-craft] What are your thoughts on intentionally "breaking the
 rules" on a collection
From: Dietrich Schulten <dietrich.schul...@googlemail.com>
To: api-craft@googlegroups.com
Content-Type: multipart/alternative; boundary=0015175cd9c66dffb004ce8c593a

--0015175cd9c66dffb004ce8c593a
Content-Type: text/plain; charset=ISO-8859-1

What is it the clients really need? Huge numbers of reps? Or a small
selection?
Anyway, I am not aware of any rule that forbids to embed the actual object
rather than linking to it.
Kind regards
Dietrich
Am 15.11.2012 18:45 schrieb "Jason Mulligan" <attac...@gmail.com>:

> I have a biz requirement that dictates a truly RESTful API will not always
> work, e.g. a collection that has 10k - 500k reps. So I proposed to my
> coworkers that we leverage the query string & "composite=true" to return an
> Array of Objects instead of an Array of URIs (relative or absolute, doesn't
> matter). This allows our API to default to RMM3, and when needed, we can
> enable a "2.5" result on collections only. The implicit value be "false".
>
> The Objects in the Array would be the result of the URIs; there's no deep
> dive / recursion possible; it is simply a method to reduce requests under
> certain constraints.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "API Craft" group.
> To unsubscribe from this group, send email to
> api-craft+unsubscribe@googlegroups.com.
> Visit this group at http://groups.google.com/group/api-craft?hl=en.
>
>
>

--0015175cd9c66dffb004ce8c593a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">What is it the clients really need? Huge numbers of reps? Or=
 a small selection? <br>
Anyway, I am not aware of any rule that forbids to embed the actual object =
rather than linking to it.<br>
Kind regards <br>
Dietrich </p>
<div class=3D"gmail_quote">Am 15.11.2012 18:45 schrieb &quot;Jason Mulligan=
&quot; &lt;<a href=3D"mailto:attac...@gmail.com">attac...@gmail.com</a>&gt;=
:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a biz requirement that dictates a truly RESTful API will not always =
work, e.g. a collection that has 10k - 500k reps. So I proposed to my cowor=
kers that we leverage the query string &amp; &quot;composite=3Dtrue&quot; t=
o return an Array of Objects instead of an Array of URIs (relative or absol=
ute, doesn&#39;t matter). This allows our API to default to RMM3, and when =
needed, we can enable a &quot;2.5&quot; result on collections only. The imp=
licit value be &quot;false&quot;.<div>
<br></div><div>The Objects in the Array would be the result of the URIs; th=
ere&#39;s no deep dive / recursion possible; it is simply a method to reduc=
e requests under certain constraints.</div><div><br></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;API Craft&quot; group.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:api-craft%2=
Bunsubscribe@googlegroups.com" target=3D"_blank">api-craft+unsubscribe@goog=
legroups.com</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/group/api-craft?hl=
=3Den" target=3D"_blank">http://groups.google.com/group/api-craft?hl=3Den</=
a>.<br>
=A0<br>
=A0<br>
</blockquote></div>

--0015175cd9c66dffb004ce8c593a--