Afternoon all, The HTTP PATCH verb is interesting in that it allows you to update a representation without having to transfer the entire thing. It's a space-time tradeoff in that it's a smaller transfer but you then have to generate and apply the patch, but for large/complex representations and remote (e.g. iPhone) users it could provide significant benefit. I wouldn't suggest that it be required at this time given lack of implementation (e.g. Apache) support but I've added a reference to it to OCCI as it will be useful for some applications and I'd rather provide the functionality than have people invent it. It's worth noting that PATCH first made an appearance (along with LINK and UNLINK) in the first HTTP RFCs but wasn't included in more recent releases due to lack of implementations. Sam ---------- Forwarded message ---------- From: Mark Nottingham <mnot@mnot.net> Date: Fri, Oct 16, 2009 at 1:48 AM Subject: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt To: HTTP Working Group <ietf-http-wg@w3.org>

New version (-15) has been submitted for draft-dusseault-http-patch-15.txt. http://www.ietf.org/internet-drafts/draft-dusseault-http-patch-15.txt Sub state has been changed to AD Follow up from New Id Needed

Diff from previous version: http://tools.ietf.org/rfcdiff?url2=draft-dusseault-http-patch-15

IETF Secretariat.

-- Mark Nottingham http://www.mnot.net/