Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 adc@toolazydogs.com does not designate 209.85.160.52 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Canonical sources for information
From: Alan Cabrera <adc@toolazydogs.com>
In-Reply-To: 
 <CAFG6u8G7gs5ZYa7xREeqAZbihZ6fxAWEauSm+BB1zcfUoy8Eaw@mail.gmail.com>
Date: Wed, 29 May 2013 08:26:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <08E28566-2535-4448-A90C-7327A4581CA7@toolazydogs.com>
References: 
 <CAFG6u8F3z-jfHBKGwui45YPW9p+AHx8-QM=He_VDR0iKagbNJA@mail.gmail.com>
 <CAOGo0VZbBmZiVz0rML-4FjGZR0Uvi_9XtyLM0c3ZdA=SPWTK3Q@mail.gmail.com>
 <5112E265-B761-4BD2-91F8-96D22D2DE089@toolazydogs.com>
 <223E4DC4-F88F-4CC9-80C6-5B8D9C1C2C8C@pc-tony.com>
 <CAFG6u8HLjsDkhCM2p0y6CcC91hdVsSk_bfOfUs6PkFfb7F70JQ@mail.gmail.com>
 <CAOGo0VbZvdcwrvH69tRscmAgVQyMhprxGGKnE2jWtgiEXanLCQ@mail.gmail.com>
 <CAFG6u8F7a0esc-u=A9srJkLcNBCqkHggfMa3E+7034Z+SN2ZCw@mail.gmail.com>
 <52AA7616-8FCA-4594-817B-F7C0404B0B76@toolazydogs.com>
 <003301ce5c35$bc0be000$3423a000$@acm.org>
 <D3F746A9-9396-4B6D-B684-89DB4EF68F12@toolazydogs.com>
 <20130529125110.GD21207@pctony-mbp.mac>
 <38BEE2AB-BF00-4767-B602-8D6AD8E72620@toolazydogs.com>
 <CAFG6u8G7gs5ZYa7xREeqAZbihZ6fxAWEauSm+BB1zcfUoy8Eaw@mail.gmail.com>
To: infrastructure-dev@apache.org


On May 29, 2013, at 6:36 AM, Sam Ruby <rubys@intertwingly.net> wrote:

> On Wed, May 29, 2013 at 9:10 AM, Alan Cabrera <adc@toolazydogs.com> =
wrote:
>>=20
>> Having whimsy change would be a bad thing.  I need a simple, =
canonical, REST API to access data and was hoping whimsy would be that =
API.  It makes no sense having a myriad of scripts and libraries all =
with the same cookie cut code to access lower levels of information.  =
All of that stuff should be behind an API like whimsy.  Then you'll have =
a single choke point to control access.
>=20
> A few things...
>=20
> 1) I wrote that JSON code on a whim, and it can be changed very
> quickly.  As in an svn commit on my machine and an svn up on whimsy.
> And that code was written long before your request.  And as far as I
> know, you are the first user of it (IIRC, danielsh opted for the
> text/plain interface).  Net: it is software.  It can be changed
> quickly.

No worries.  I assume that you will make a reasonable effort to keep =
things stable and backward compatible.

What kind of SLA are you providing with your service?  ;)

> 2) looking at that code[1], I immediately spot a bug.  While the HTML
> interface will filter out data that a non-member couldn't see, the
> JSON interface doesn't.  So I already need to open up that code.
> While I am in there, if you have any requests, now would be a good
> time.

Ok, atm I don't think I rely on that data.  What data would that be?

> 3) that code is just a view.  The underlying model is shared between
> several services.  Adding a new view is very trivial.

Yeah, it's the coalescing of data from disparate sources that makes your =
service so attractive to me.


Regards,
Alan