Example service: issue tracker

Jørn Wildt edited this page Jun 3, 2015 · 12 revisions

You can try a live example of Mason applied to a simple issue tracker service. Just point your browser to the "landing page" of the service and start exploring. Mason is designed to guide client developers with hints embedded in the responses using the @meta element, so the service should be self explaining.

I strongly recommend you use the generic Mason client which is a Windows program that handles all of the features in Mason which means you can both browse the existing data as well as modify or delete it and add new stuff.

The issue tracker (using Mason Draft 2) can be found here: http://mason-issue-tracker.azurewebsites.net/resource-common. Feel free to try it yourself.

Please note:

  • The service and database is reset every 15 minutes.
  • There is a maximum of 10kb for file uploads.
  • It runs on SQLite and is not exactly blazing fast.
  • You must use the X-Http-Method-Override header for other HTTP methods than GET and POST (this is due to some stupid server restrictions).

You can also find an older version of the issue tracker (using Mason Draft 1) hosted by cBrain here: http://mason-issue-tracker.cbrain.net/resource-common.

Service description

The service manages issues, with file attachments, organized in projects. You can add, edit and delete both issues, attachments and projects.

It also have a primitive query mechanism for issue searching - look for the link relation "issue-query" to find a link template for issue searching.

So far there is no implementation of users and authorization.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.