[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-61) CAMP is vague about which HTTP methods each resource supports
[ http://tools.oasis-open.org/issues/browse/CAMP-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34070#action_34070 ]
Alex Heneveld commented on CAMP-61:
-----------------------------------
Would *really* like to see this information on each resource, i.e. in the sections in Chap 5 (e.g. "Platform MUST support POST and a successful invocation resulting in an AssemblyTemplate as described in 4.x.").
In other words each Resource clearly says which HTTP methods (beyond GET) are supported.
Ideally I think this will probably result in some material from Chap 6 being moved out (e.g. suspending, PDP). I think that results in a better structure in any event -- as 6 can then be just technical details of status codes and media types, and is not mixing in platform semantics.
> CAMP is vague about which HTTP methods each resource supports
> -------------------------------------------------------------
>
> Key: CAMP-61
> URL: http://tools.oasis-open.org/issues/browse/CAMP-61
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Bug
> Components: Spec
> Reporter: Gilbert Pilz
> Assignee: Gilbert Pilz
> Priority: Critical
>
> CAMP (wd08) is vague about which HTTP method each resource supports. If you read the spec carefully you can figure out that, for example, AssemblyTemplate supports POST, but you can't tell if Assembly supports POST. For conformance purposes, CAMP needs to be crystal clear about which resources MUST accept which HTTP methods. Implementations should be allowed to extend this list by accepting additional HTTP methods.
--
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]