[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-34) Immutable and read-only attributes in the REST world
[ http://tools.oasis-open.org/issues/browse/CAMP-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32140#action_32140 ]
Anish Karmarkar commented on CAMP-34:
-------------------------------------
I forgot about this issue and filed issue 41 (which obviously is a dup).
For the PUT part, this is what I would like to propose as a direction:
a) Are clients are allowed to send RO/immutable attributes: YES
b) Are clients required to send RO/immutable attribute: YES, if they did exist in the last GET.
c) Can client change immutable attribute in a PUT request: NO (MUST NOT)
d) if the value of the RO/immutable attribute has been changed by the client the server MUST throw a 4xx error
To make things unambiguous, remove the attribute constraints 'Mutability' and 'Writable' and instead use new attribute constraints:
Unchangeable, Server-Changeable, Client-Chanageable (or equivalent)
This is independent of what we do wrt PATCH.
> Immutable and read-only attributes in the REST world
> ----------------------------------------------------
>
> Key: CAMP-34
> URL: http://tools.oasis-open.org/issues/browse/CAMP-34
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Bug
> Components: Spec
> Reporter: Anish Karmarkar
> Assignee: Adrian Otto
>
> We have a notion of immutable attributes (section 5.2.2) and read-only attribute (section 5.2.3) for resources. By definition these attributes cannot be changed by the client. One example of such an attribute is 'created' (section 5.3.4). When a client updates the resource (using PUT), does it include these attributes? The semantics of PUT say that PUT overwrites everything at the specified resources. This implies that the client cannot exclude any attributes. PUT cannot be used for partial updates (see http://tech.groups.yahoo.com/group/rest-discuss/message/17421). This brings up some interesting questions:
> 1) What should the server do if the attribute 'created' (or a similar attribute) is not included in the PUT? Error, ignore the omission, or something else?
> 2) What should the server do if the attribute 'created' (or a similar attribute) is changed by the client in the PUT? Error, ignore the change, or something else?
> 3) Is the server required to check changes to read-only attributes?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]