REST API

As you may have noticed, John Rouillard is putting quite some time into
getting the REST-API into shape for a first release.

I'm now taking the private discussion I had with John to the list so
that more people are informed about what is done.

John: I've not yet had time to test your changes from the weekend so
forgive me if I've overlooked something that is already implemented.

As far as I can tell what is still open is
- A version Identifier after /rest, e.g. /rest/.../v1 or /rest/.../1 for
  the initial release. Your latest commit is ambiguos, it says that
  /rest returns supported version but then goes on with /rest/data --
  which should then be /rest/.../0/data?
  Or should we make the initial version v0?
  Should we have some prefix before the version (indicated by ... above)
  This could be done in class Routing, which would become more
  complicated when we add additional versions.
- Hard-coded /data: Are you working on this? If not I think I know the
  Roundup-API well enough to fix this
- Hard-coded class in /summary: This should also be fixed, I have quite
  some trackers that simply don't have an 'issue' class.
  The code there (and the permission checks) should probably be a lot
  more dynamic, we could leave out the status if no permission etc.
- Docs :-)

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]