[
https://issues.apache.org/jira/browse/CLOUDSTACK-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551702#comment-13551702
]
Rohit Yadav commented on CLOUDSTACK-865:
----------------------------------------
Yes, api_refactoring was mostly internal optimization.
The changes are mostly for developers who would want to write new apis, or
pluggable services or acl plugins, so I'll document those on cwiki.
For users there are few notes:
1. While making calls, use of UUID is recommended. For pre 3.x CloudStack APIs
both internal ID (long int) and UUID (String) will work and for new APIs (Post
3.x like listS3s, autoscale etc.) UUID enforcement was done, so internal IDs
won't work with those api calls. This is to say: For new and old apis UUID is
encouraged to be used, for old apis IDs will still work.
2. As part of both xml and json API response, the version field name
"cloudstack-version" will hold the CloudStack mgmt server version.
3. In response if any parameter is empty it's not serialized i.e. sent as part
of response.
There is no other change AFAIK, for response Min can comment on it.
> Document API Refactoring
> -------------------------
>
> Key: CLOUDSTACK-865
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-865
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Reporter: Radhika Nair
> Assignee: Jessica Tomechak
> Fix For: 4.1.0
>
>
> Document API Refactoring
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
