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: 103376,c70dc869310ffb51
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Path: 
 g2news1.google.com!news4.google.com!feeder3.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!213.75.85.109.MISMATCH!newsfeed.kpn.net!pfeed09.wxs.nl!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 10:40:12 +0000
Organization: A noiseless patient Spider
Message-ID: <m2ei8bn78z.fsf@pushface.org>
References: <4d335a76$0$43992$742ec2ed@news.sonic.net>
	<2b5cd851-c148-41f4-95e7-14f235846e6a@q18g2000vbk.googlegroups.com>
	<op.vpfanufdule2fv@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="32559"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/iotuJUyKLR4L+v0u1ZJqDnWjT68xYkmc="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin)
Cancel-Lock: sha1:8ZM7PVcmNJLiH2cI9nwLHSnVhoo=
	sha1:jW5yssiF9L7rdjIHaiJWaU4g/NA=
Xref: g2news1.google.com comp.lang.ada:16476
Date: 2011-01-17T10:40:12+00:00
List-Id: <comp.lang.ada>

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

>                                                 there is *never*
> something like stateful with web process. This is a fundamental
> consequence of the  client browsing process. “Stateful web server”
> concept makes no sense. As  the user can go back and forward in
> his/her navigation history, the only  possible state must be stored in
> pages stored in the browser, and if ever  needed, these states
> informations must be transmitted to the web server  via POST
> (preferably, personal feeling). In the web, there is a per-page  state
> at the client side, not a per-cession state at the server side.

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.