openstack team mailing list archive

Thread
Date

Re: [Glance] Using HTTP PATCH

To: Mark Nottingham <mnot@xxxxxxxx>
From: Brian Waldon <brian.waldon@xxxxxxxxxxxxx>
Date: Thu, 24 May 2012 05:06:58 -0700
Cc: "openstack@xxxxxxxxxxxxxxxxxxx \(openstack@xxxxxxxxxxxxxxxxxxx\)" <openstack@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <D5A3E421-7D8F-48D8-B6DC-770F76191554@mnot.net>

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 research on PATCH, as I hadn't discovered this yet. I was just planning on using the method to be more semantically correct: allowing requests with a content-type of application/json and a partial representation of an entity. Is there anything about PATCH that would disallow that? 

Waldon

Follow ups

Re: [Glance] Using HTTP PATCH
From: Mark Nottingham, 2012-05-24

References

[Glance] Using HTTP PATCH
From: Brian Waldon, 2012-05-23
Re: [Glance] Using HTTP PATCH
From: Mark Nottingham, 2012-05-24