When creating a REST API are there any naming conventions for designating a read only property? -


i thinking useful if property name signaled readonly.

take object example:

{     "id":"12154",     "name":"some name",     "email":"email@something.com",     "joindate":"05/04/2012" } 

id , joindate of course properties readonly , not allow change through put/post request. there type of convention marking these such? thinking of doing underscores:

{     "_id":"12154",     "name":"some name",     "email":"email@something.com",     "_joindate":"05/04/2012" } 

there no naming convention read-only properties in rest. should, of course, feel free establish whatever conventions own api. fiver said in comment, should make sure documented, or conventions combination of (a) confusing, , (b) noise.


Comments

Popular posts from this blog

google api - Incomplete response from Gmail API threads.list -

Installing Android SQLite Asset Helper -

Qt Creator - Searching files with Locator including folder -