Re: [Openstack] [Glance] Using HTTP PATCH

2012-05-24 Thread Mark Nottingham
On 24/05/2012, at 6:22 AM, Brian Waldon wrote: Hey guys, I'm considering using PATCH rather than PUT for image updates in the v2 Image API, but I wanted to make sure there weren't any major blockers that I might be missing. As far as I can tell, the python libraries we use in Glance

Re: [Openstack] [Glance] Using HTTP PATCH

2012-05-24 Thread Brian Waldon
On May 24, 2012, at 4:12 AM, Mark Nottingham wrote: The other limitation is having defined and registered patch formats. The IETF is currently working on one for JSON; it should be progressing soon. http://tools.ietf.org/html/draft-ietf-appsawg-json-patch I guess I haven't done enough

Re: [Openstack] [Glance] Using HTTP PATCH

2012-05-24 Thread Mark Nottingham
On 24/05/2012, at 10:06 PM, Brian Waldon wrote: On May 24, 2012, at 4:12 AM, Mark Nottingham wrote: The other limitation is having defined and registered patch formats. The IETF is currently working on one for JSON; it should be progressing soon.

[Openstack] [Glance] Using HTTP PATCH

2012-05-23 Thread Brian Waldon
Hey guys, I'm considering using PATCH rather than PUT for image updates in the v2 Image API, but I wanted to make sure there weren't any major blockers that I might be missing. As far as I can tell, the python libraries we use in Glance support it (httplib2, requests). However, I discovered

Re: [Openstack] [Glance] Using HTTP PATCH

2012-05-23 Thread Brian Waldon
Above all, I want to keep the API spec as clean as possible. We would have to design a way to communicate what method we use if we make it configurable by the backend like you suggest. That seems like its moving away from cleanliness rather than toward. I'm more interested in first hearing if

Re: [Openstack] [Glance] Using HTTP PATCH

2012-05-23 Thread Nick Barcet
On 05/23/2012 09:39 PM, Joshua Harlow wrote: Is there anyway u can just make it a configuration option? v2imagemethod = ‘PUT’... This would make sense as rfc 5789 is only 2 years old, which means that there must be numerous firewalls and proxies which may not have been updated yet in

Re: [Openstack] [Glance] Using HTTP PATCH

2012-05-23 Thread Brian Waldon
Relevant links: https://review.openstack.org/#/c/7716/ http://tools.ietf.org/html/rfc5789 http://weblog.rubyonrails.org/2012/2/25/edge-rails-patch-is-the-new-primary-http-method-for-updates/ On May 23, 2012, at 1:22 PM, Brian Waldon wrote: Hey guys, I'm considering using PATCH rather than

Re: [Openstack] [Glance] Using HTTP PATCH

2012-05-23 Thread John Postlethwait
Patch certainly seems more semantically proper in this context, and I love being semantically proper using HTTP… That being said I am not currently sure of any places where this might be a problem. There was mention of the firewall issues, but I don't know if that is necessarily true. Do