W3C home > Mailing lists > Public > public-html-comments@w3.org > April 2011

Re: [Fwd: Re: PUT and DELETE methods in 200 code]

From: Subbu Allamaraju <subbu@subbu.org>
Date: Fri, 1 Apr 2011 18:07:33 -0700
Cc: Sam Ruby <rubys@intertwingly.net>, public-html@w3.org, Julian Reschke <julian.reschke@gmx.de>, nathan@webr3.org, public-html-comments@w3.org, www-archive <www-archive@w3.org>
Message-Id: <D6C97E72-67C6-46B1-9D8C-2EDC12B5A767@subbu.org>
To: mike amundsen <mamund@yahoo.com>
Do you need the conditional headers as form parameters? The agent should be able to replay those headers.

Subbu

On Apr 1, 2011, at 5:50 PM, mike amundsen wrote:

> Cross-posting to related groups:
> 
> I've posted a document[1] that shows one way in which HTML FORMS can
> support PUT/DELETE w/o the need for plug-ins or scripting. It's a
> quick draft but I think it covers the basics.
> 
> If this is not in the desired format let me know.
> 
> 
> [1] http://amundsen.com/examples/put-delete-forms/
> 
> mca
> http://amundsen.com/blog/
> http://twitter.com@mamund
> http://mamund.com/foaf.rdf#me
> 
> 
> #RESTFest 2010
> http://rest-fest.googlecode.com
> 
> 
> 
> 
> On Fri, Apr 1, 2011 at 16:24, Sam Ruby <rubys@intertwingly.net> wrote:
>> On 04/01/2011 03:29 PM, Julian Reschke wrote:
>>> 
>>> On 01.04.2011 21:04, Sam Ruby wrote:
>>>> 
>>>> On 04/01/2011 02:01 PM, Nathan wrote:
>>>>> 
>>>>> fwd'ing to some relevant lists - would be very happy to see a proper
>>>>> response from W3C / HTML WG chairs, particularly the question "And
>>>>> *where* should this activity happen?"
>>>> 
>>>> Where is in bug reports:
>>>> 
>>>> http://dev.w3.org/html5/decision-policy/decision-policy.html
>>>> 
>>>> Should you (or anyone) wish to escalate a proposed RESOLUTION by the
>>>> editor, you will be encouraged to join the working group and participate
>>>> by creating a proposal and participating in the discussion:
>>>> 
>>>> http://www.w3.org/html/wg/#join
>>>> 
>>>>> best, nathan
>>>> 
>>>> - Sam Ruby
>>> 
>>> I'm currently interested in a discussion that leads to something that
>>> *could* be added to the HTML spec, and might lead to clarifications in
>>> the HTTPbis specs.
>>> 
>>> I don't think an issue tracker is the right place for that.
>> 
>> In that case, discussions can happen anywhere; but those that could lead to
>> changes to the W3C HTML spec should occur on public-html to ensure that all
>> of the right people see it.
>> 
>>> Best regards, Julian
>> 
>> - Sam Ruby
>> 
>> 
> 
Received on Saturday, 2 April 2011 01:11:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 June 2011 00:14:06 GMT