Is my JavaScript browser for hypermedia JSON APIs as RESTful as I think it is? - API Craft

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Is my JavaScript browser for hypermedia JSON APIs as RESTful as I think it is?
Received-SPF: pass (google.com: domain of mikekelly...@gmail.com designates 209.85.214.169 as permitted sender) client-ip=209.85.214.169;
MIME-Version: 1.0
In-Reply-To: <647d3224-9889-456a-b2b3-59f8f3f7fcbe@googlegroups.com>
References: <647d3224-9889-456a-b2b3-59f8f3f7fcbe@googlegroups.com>
Date: Wed, 17 Oct 2012 13:14:34 +0100
Message-ID: <CANqiZJYVWic_85JaDTuGJJoH_ZTBqmu0UCStwmPejvFsm+3...@mail.gmail.com>
Subject: Re: [api-craft] Is my JavaScript browser for hypermedia JSON APIs as
 RESTful as I think it is?
From: Mike Kelly <mikekelly...@gmail.com>
To: api-craft@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

Hi Dave,

Looks good. Have you seen the hal browser? That's pretty similar to this.

Did the "hypermedia" property come out of your work on the browser or
the other way around?

Cheers,
M

On Wed, Oct 17, 2012 at 5:42 AM, Dave Gauer <ratfac...@gmail.com> wrote:
> Hello,
>
> I would genuinely appreciate some expert opinions regarding hm-json Browser,
> a JavaScript client for hypermedia JSON APIs:
>
> https://bitbucket.org/ratfactor/hm-json-browser
>
> (Documentation, the tiny source code, and most importantly, LIVE DEMO at the
> link above.)
>
> I believe it passes the smell test for REST because it is:
>
> Discoverable - the entire API can be traversed from a single starting URI
> Fully self-documented - any HTTP method is supported (and the browser
> natively understands GET, PUT, POST, OPTIONS, and DELETE)
> Encourages RESTful resources and a generality of interfaces (but being a
> client, can't actually enforce good RESTful design)
>
> And though it's other features have nothing to do with REST, it also allows
> you to browse to templated URIs (level 1 variable expansion only), PUT and
> POST data through the browser, see titles and descriptions/instructions for
> the resources you are manipulating, and generally let you use the full range
> of HTTP's capabilities like I think we all wish Web browsers could.
>
> I believe it will make any project which uses it extremely
> developer-friendly and I'm happy with it.
>
> But I'm wondering if the browser (and my simplistic demo API) would be
> considered "real REST" by a true aficionado?   REST's "code on demand"
> constraint is explicitly optional, so I feel safe there.  But I don't
> address caching at all, and I'm wondering if that's enough to knock hm-json
> Browser out of the REST category altogether.  I could add caching, but it's
> really not a high priority for such a small tool and feels to me like it
> would be a pretty arbitrary requirement.
>
> I have absolutely no interest in buzzwords and came to REST out of a true
> admiration for elegant API design.  If there are ways this could be
> improved, I would absolutely love to hear about them.
>
> Thanks,
>
> -Dave Gauer
>
> --
> 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.
>
>



-- 
Mike

http://twitter.com/mikekelly85
http://github.com/mikekelly
http://linkedin.com/in/mikekelly123
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
