Open Stack

JC,

The API doesn't define PUT operations on lists, so we don't have this issue. To update the membership of the list, one removes and adds elements to it. To update a specific element, one operates directly on the element.

Thanks,
Youcef

From: JC Martin [mailto:jcmartin at ebaysf.com]
Sent: Thursday, November 1, 2012 6:35 PM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [Quantum][LBaaS] LBaaS API 1.0 spec draft

Youcef,

How do you distinguish between removing elements in a list and updating only some members ?
For example, if you update the members attribute in a pool, is the semantic that you replace the list of members with the one in the put request ?
Is the rule that attribute values are always replaced by the values in put request (even lists) ?

Thanks,

JC


From: Youcef Laribi <Youcef.Laribi at eu.citrix.com<mailto:Youcef.Laribi at eu.citrix.com>>
Reply-To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thu, 1 Nov 2012 05:05:58 +0000
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Quantum][LBaaS] LBaaS API 1.0 spec draft

Let's add a note that all update operations adopt patch semantics (like Quantum does)
Good point. Yes, the semantics of "PUT" in REST is not universally agreed upon :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121102/791dea78/attachment.html>