- From: Ray Polk <raypolk@gmail.com>
- Date: Thu, 19 Jan 2012 13:01:49 -0700
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: ietf-http-wg@w3.org
Received on Thursday, 19 January 2012 20:02:17 UTC
My question is: should/does the HTTP spec absorb the most widely accepted of these separately defined methods? put another way: should this group anoint the most widely used of the methods from that registry as first class HTTP methods? It seems like such a thing would help with adoption. On Thu, Jan 19, 2012 at 12:53 PM, Julian Reschke <julian.reschke@gmx.de>wrote: > On 2012-01-19 20:40, Ray Polk wrote: > >> Last noob question of the day: >> >> PATCH (http://tools.ietf.org/html/**rfc5789<http://tools.ietf.org/html/rfc5789>) >> isn't listed as a spec >> defined method. What's the practice when it comes to additive RFCs like >> PATCH? >> >> Thanks for your patience, >> Ray >> > > I'm not sure I understand the question. > > New methods can be defined in separate specs, and have been. > > The only new thing is that we now have a registry for them. > > Best regards, Julian >
Received on Thursday, 19 January 2012 20:02:17 UTC