-
Notifications
You must be signed in to change notification settings - Fork 1
Home
mohsinhijazee edited this page Sep 13, 2010
·
18 revisions
A pure Java/Swing based Dedomenon client and a Java Language Binding for REST API.
- For the PUT and POST requests, payload should always be referred to as resource
- For POST requests, the URL of the created resource should be always in an array.
- The id of the parent resource is provided in either the URL like http://myhost.org/databases/4/entities/3.json or it can be like this: http://myhost.org/entities.json?database_id=12&id=9. Do make sure that these ids can be passed as URLs as well. For example database_id parameter might be supplied as database_url and this would contain the URL of the database. Yet needs more thinking.
- What a DELETE response should be in case of succuess? For now, its only “deleted” (note that double quotes are part of the response) But what a better way can be? And in case of failure, what we’re’ doing?
- While getting an entity, its database_url field is absent instead database_id is available. The problem is in the rest/entities/_entity.xml.builder
- Check if the validation of a Resource in PUT and POST calls is thorough or not.