dracoblue / hateoas-client-js Goto Github PK

Currently rest-client.js only supports atom feeds and common convention for json-links. It would be cool, if there was an implementation for the HAL Specification MediaType, too. http://stateless.co/hal_specification.html

It should be also possible to use a filter-function instead of a *, to for instance breadth search only "next-archive"-links in a atom archive.

It would be nice if rest-client.js was available via bower.

A proper name is "rest-client-js". I registered the package already.

$ bower info rest-client-js
bower cached        git://github.com/DracoBlue/rest-client-js.git#0.1.0
bower validate      0.1.0 against git://github.com/DracoBlue/rest-client-js.git#*

{
  name: 'rest-client-js',
  homepage: 'https://github.com/DracoBlue/rest-client-js',
  version: '0.1.0'
}

Available versions:
  - 0.1.0

The first call to agent.get() should store the response (or the parsed result) and subsequent calls should return the cached result.

Perhaps supply a .refresh() or .reset() method to delete the cache?!

Hi

First off I wanna say I really like the idea of HAL and this generic rest client. I've been looking for something like this for a while.

There are some improvements to this project I'd like to make. I might end up writing a variant of this but thought I'd share my ideas and see what you thought.

Instead of (or as well as) using callbacks, return the jQuery promise from $.ajax()

This would allow the following:

agent.get()
  .then(myFn)
  .then(myFn2)

When calling agent.navigate() return a new HttpAgent and leave the original unchanged.

This would allow users to cache agents which point to different resources.

var root = new HttpAgent('/api');

var products = root.navigate('products'); // /api/products

var orders = root.navigate('orders'); // /api/orders