Skip to content
carterpage edited this page Jul 5, 2011 · 6 revisions

Hold your horses... we'll get there. In the mean time, please take a look at the Issues. You can request features that way.

Our thoughts:

  1. A mechanisms to expose meta data via XML/JSon/HTML, with cross-referencing links. Meta data can include structure meta-data of available data that's exposed, as well as a high level "API Map" (akin to a site Map).
  2. A RESTful client that knows how to take advantage of Yoga data.
  3. A fine-grained mechanism to update resource properties (Thanks @vambenepe!)
  4. Query aliases. Some do not want to expose full selector functionality in production. Simple aliasing that requires no coding is an quick solution. (e.g. Alias "/user/1.json?selector=:(friends)" to "/friends/1.json" with a one-line configuration change in run-time.)