> 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.