From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,c70dc869310ffb51
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news2.google.com!news3.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Annoucing memcache-ada 0.1
Date: Mon, 17 Jan 2011 19:57:47 +0000
Organization: A noiseless patient Spider
Message-ID: <m262tnmhfo.fsf@pushface.org>
References: <4d335a76$0$43992$742ec2ed@news.sonic.net>
	<2b5cd851-c148-41f4-95e7-14f235846e6a@q18g2000vbk.googlegroups.com>
	<op.vpfanufdule2fv@garhos> <m2ei8bn78z.fsf@pushface.org>
	<op.vpf86sjbule2fv@garhos>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: mx02.eternal-september.org;
 posting-host="dFCm8HWntFqmDIilBLqEJQ";
	logging-data="26625"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19VzbUapfBKoQM3q58vLYt/NTIOmyRtrSo="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin)
Cancel-Lock: sha1:AJm1puhtMDdTeUf+Ak1isu1r/Mc=
	sha1:Gi4iEQw62T2vOMcsqbJClD801Og=
Xref: g2news2.google.com comp.lang.ada:17465
Date: 2011-01-17T19:57:47+00:00
List-Id: <comp.lang.ada>

"Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr> writes:

> Le Mon, 17 Jan 2011 11:40:12 +0100, Simon Wright <simon@pushface.org>
> a écrit:
>> Using AJAX, there is certainly state within one page... but even
>> excluding that, there clearly _is_ per-session state on the server; of
>> course, the browser has to identify the session concerned before the
>> server can know where to continue from.
>
> I see your point, you are right too. I lacked some precision: this
> depends on the involved functionality. If you are serving pages whose
> access  requires some right (like browsing a private forum), then it
> just requires  a cession state, and the server is able to hold it. On
> the other hand,  richer web applications (the ones I was implicitly
> referring too),  requires a state stored in the page, or at least a
> reference to a state  for that page. If the user hit the Back button,
> any request made from that  page will have to send the state
> associated with that previous page.  Imagine a user clicking a Submit
> button in a page retrieved from the  browser cache he/she reached
> after hitting Back in the browser; then  imagine he/she already click
> this button before he came back to it (this  is a typical case of
> error if the server handles the second request with  the sate
> associated to the last requested page).

Yes, this is a real problem with AJAX applications; you press Back and
end up in something you'd forgotten about half an hour ago. And Forward
will not recover.