Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #14543

Re: GET vs POST in AJAX

Message-ID <1598106.oMNUckLgyt@PointedEars.de> (permalink)
From Thomas 'PointedEars' Lahn <PointedEars@web.de>
Organization PointedEars Software (PES)
Date 2012-06-17 09:06 +0200
Subject Re: GET vs POST in AJAX
Newsgroups comp.lang.javascript
References <bcc85577-4540-4c88-8c4a-4fd9492c6f89@googlegroups.com> <jrhpod$g06$1@news.albasani.net> <z15Dr.17851$FV6.10884@newsfe05.iad> <jriogu$4um$1@news.albasani.net> <KZ5Dr.15185$ji7.2529@newsfe20.iad>
Followup-To comp.lang.javascript

Followups directed to: comp.lang.javascript

Show all headers | View raw


Daniel Pitts wrote:

> On 6/16/12 12:58 PM, Stefan Weiss wrote:
>> On 2012-06-16 21:22, Daniel Pitts wrote:
>>> On 6/16/12 4:13 AM, Stefan Weiss wrote:
>>>> As you say, the difference is mostly semantic. In a nutshell,
>>>> - GET retrieves information from the server. It should not have any
>>>> other side effects changing the state on the server, or at least the
>>>> client may assume that the request is "safe".
>>
>>> Actually, I recall reading somewhere that "GET" need only be idempotent.
>>> The first call is allowed to change server state, but calling it over
>>> and over again will have no further effect.
>>
>> I've never heard that before. It would be be interesting to know where
>> you read that.
> I don't remember where I first read that, but here is a top result for
> the Google search "get method idempotent"
> 
> <http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html>

This is Usenet.  Please do not only post URLs of resources which you *think* 
support your position (for the dedicated reader to switch medium to find out 
whether it really does), but *make an argument* using the resource as 
reference (best by citing it *and* quoting the relevant parts).  Refer
to Stefan's posting for a good example how that can be done.


PointedEars
-- 
Anyone who slaps a 'this page is best viewed with Browser X' label on
a Web page appears to be yearning for the bad old days, before the Web,
when you had very little chance of reading a document written on another
computer, another word processor, or another network. -- Tim Berners-Lee

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

GET vs POST in AJAX CODEY <ed.pataky@gmail.com> - 2012-06-15 18:16 -0700
  Re: GET vs POST in AJAX Andrew Poulos <ap_prog@hotmail.com> - 2012-06-16 13:31 +1000
    Re: GET vs POST in AJAX CODEY <ed.pataky@gmail.com> - 2012-06-21 15:43 -0700
  Re: GET vs POST in AJAX Jason C <jwcarlton@gmail.com> - 2012-06-15 21:14 -0700
  Re: GET vs POST in AJAX Stefan Weiss <krewecherl@gmail.com> - 2012-06-16 13:13 +0200
    Re: GET vs POST in AJAX Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-06-16 12:22 -0700
      Re: GET vs POST in AJAX Stefan Weiss <krewecherl@gmail.com> - 2012-06-16 21:58 +0200
        Re: GET vs POST in AJAX Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-06-16 13:26 -0700
          Re: GET vs POST in AJAX Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-17 09:06 +0200
            Re: GET vs POST in AJAX Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-06-17 20:57 -0700
              Re: GET vs POST in AJAX Stefan Weiss <krewecherl@gmail.com> - 2012-06-18 15:23 +0200
                Re: GET vs POST in AJAX Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-18 20:17 +0200
                Re: GET vs POST in AJAX Stefan Weiss <krewecherl@gmail.com> - 2012-06-19 03:41 +0200
                Re: GET vs POST in AJAX Andrew Poulos <ap_prog@hotmail.com> - 2012-06-19 12:25 +1000
                Re: GET vs POST in AJAX Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-19 19:19 +0200
                Re: GET vs POST in AJAX Dr J R Stockton <reply1225@merlyn.demon.co.uk.not.invalid> - 2012-06-19 20:44 +0100
              Re: GET vs POST in AJAX Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-18 20:14 +0200

csiph-web