I noticed a few things about the new 1.1 spec that I thought I'd give feedback on:
1. Set Queue Metadata
A PUT operation is provided, which does a hard replace of metadata values. New
items are inserted, and existing items that are not specified are wiped.
Nova also provides a POST operation that is more sympathetic - allowing you to
update only the values specified, leaving existing unspecified items
unmodified. Could a similar operation be added to this API - since there
definitely seems like a use case for it.
2. Get a Specific Message
In the response body, the `href` field is provided as a relative URI - why?
Surely absolute URIs are more convenient for the end-user.
3. Deleting Multiple Messages
a. How does one delete multiple claimed messages? What would the URI template
look like? It is not specified whether this is possible or not.
b. If I provide a bunch of IDs, and one of them is a claimed message, what
happens? Will it be silently ignored? The behavior is undefined.
4. Read a Shard
Should these response structures be nested in a top-level "shard" object? Same
will the "List Shards" collection.
5. The request body for Post Message(s) contains malformed JSON - the `=`
should be `:`
Sorry if some of these issues have already been settled or discussed :)
Jamie
Jamie Hannaford
Software Developer II - CH [experience Fanatical Support]
Tel: +41434303908
Mob: +41791009767
[Rackspace]
Rackspace International GmbH a company registered in the Canton of Zurich,
Switzerland (company identification number CH-020.4.047.077-1) whose registered
office is at Pfingstweidstrasse 60, 8005 Zurich, Switzerland. Rackspace
International GmbH privacy policy can be viewed at
www.rackspace.co.uk/legal/swiss-privacy-policy
-
Rackspace Hosting Australia PTY LTD a company registered in the state of
Victoria, Australia (company registered number ACN 153 275 524) whose
registered office is at Suite 3, Level 7, 210 George Street, Sydney, NSW 2000,
Australia. Rackspace Hosting Australia PTY LTD privacy policy can be viewed at
www.rackspace.com.au/company/legal-privacy-statement.php
-
Rackspace US, Inc, 5000 Walzem Road, San Antonio, Texas 78218, United States of
America
Rackspace US, Inc privacy policy can be viewed at
www.rackspace.com/information/legal/privacystatement
-
Rackspace Limited is a company registered in England & Wales (company
registered number 03897010) whose registered office is at 5 Millington Road,
Hyde Park Hayes, Middlesex UB3 4AZ.
Rackspace Limited privacy policy can be viewed at
www.rackspace.co.uk/legal/privacy-policy
-
Rackspace Benelux B.V. is a company registered in the Netherlands (company KvK
nummer 34276327) whose registered office is at Teleportboulevard 110, 1043 EJ
Amsterdam.
Rackspace Benelux B.V privacy policy can be viewed at
www.rackspace.nl/juridisch/privacy-policy
-
Rackspace Asia Limited is a company registered in Hong Kong (Company no:
1211294) whose registered office is at 9/F, Cambridge House, Taikoo Place, 979
King's Road, Quarry Bay, Hong Kong.
Rackspace Asia Limited privacy policy can be viewed at
www.rackspace.com.hk/company/legal-privacy-statement.php
-
This e-mail message (including any attachments or embedded documents) is
intended for the exclusive and confidential use of the individual or entity to
which this message is addressed, and unless otherwise expressly indicated, is
confidential and privileged information of Rackspace. Any dissemination,
distribution or copying of the enclosed material is prohibited. If you receive
this transmission in error, please notify us immediately by e-mail at
ab...@rackspace.com and delete the original message. Your cooperation is
appreciated.
<<inline: image538c56.JPG>>
<<inline: image22190f.JPG>>
<<inline: imageaf72fd.JPG>>
<<inline: imageda860e.JPG>>
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
