W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: add GETAJAX verb/method in http protocol

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Thu, 24 May 2012 22:51:31 +1200
Message-ID: <4FBE12B3.8060000@treenet.co.nz>
To: ietf-http-wg@w3.org

> On 22/05/2012 14:47, Christian RIGONI wrote:
>> Hello everybody,
>>
>> I could not find this possibility in the mailing lists, so I would 
>> like to bring up this topic.
>> By working on html page developpement, I remarked that very often 
>> (but not always of course), ajax request correspond to information 
>> that are relative to an html page.
>> For example, lets define the page http://www.site.com/page.html on a 
>> server.
>> The first http verb used for this page is obviously GET.
>> Then the page is displayed by the navigator on the client.
>>
>> Now, suppose the user modify an element of the page. It can be useful 
>> to send a http GETAJAX request to http://www.site.com/page.html in 
>> order to get the information corresponding to the new element 
>> modified by the user.
>> Actually the problem is adressed by sending a http GET to another 
>> page, for example www.site.com/page_ajax.html. But may be it can be 
>> useful to send a http GETAJAX to the page http://www.site.com/page.html.
>> Another thing which can be usefull, the same page 
>> http://www.site.com/page.html may have several http ajax request to 
>> process. So an ajax_id can be added to the http GETAJAX to 
>> differentiate the ajax requests.
>>
>> I hope this request will be helpfull for you and other people.
>>
>> Sincerely.
>>
>> _Christian RIGONI_
>>
>>
On 23/05/2012 6:54 a.m., J Ross Nicoll wrote:
> Christian,
>
> I'm not sure this necessarily makes sense as a separate method; you're 
> still taking the same action (getting a resource), it's just the 
> presentation that differs. I tend to use query parameters to indicate 
> which parts of a resource I want (and an Accept header to indicate I'm 
> wanting the response as JSON/XML), is that a reason that doesn't suit?
>

The other reason is that GETAJAX would be an unknown method from the 
point of view of all existing cache infrastructure. Sending such a 
method for a URL of an already cached page template will invalidate the 
URL and wipe out any cache benefits you gain from making it static page 
with AJAX.

AYJ
Received on Thursday, 24 May 2012 10:52:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 24 May 2012 10:52:19 GMT