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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no 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,CP1252
Path: 
 g2news2.google.com!postnews.google.com!a10g2000vby.googlegroups.com!not-for-mail
From: "pascal.obry@gmail.com" <pascal.obry@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Annoucing memcache-ada 0.1
Date: Mon, 17 Jan 2011 02:50:55 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <1167f1a7-3f01-4f38-8bb8-3c50e837df7d@a10g2000vby.googlegroups.com>
References: <4d335a76$0$43992$742ec2ed@news.sonic.net>
 <2b5cd851-c148-41f4-95e7-14f235846e6a@q18g2000vbk.googlegroups.com>
 <op.vpfanufdule2fv@garhos>
NNTP-Posting-Host: 82.124.201.129
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1295261455 16132 127.0.0.1 (17 Jan 2011 10:50:55
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 17 Jan 2011 10:50:55 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: a10g2000vby.googlegroups.com; posting-host=82.124.201.129;
 posting-account=PEdGtgoAAACjNhf4BGsFw-AboVux6xYy
User-Agent: G2/1.0
X-HTTP-Via: 1.1 lancelot:3128 (squid/2.7.STABLE9)
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1.16)
 Gecko/20110107 Iceweasel/3.5.16 (like Firefox/3.5.16),gzip(gfe)
Xref: g2news2.google.com comp.lang.ada:17449
Date: 2011-01-17T02:50:55-08:00
List-Id: <comp.lang.ada>


Yannick,

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

Well yes and no. In AWS the only token sent is a cookie for a per user
state.

We also support per-page state, see Web_Block technology where a MD5
is
auto-magically injected into each page. Basically:

   1. there is a state on the server, user can (via the callback)
update,
      a context object.

   2. when sending the response to the web browser a MD5 of the full
context
      data is created.

   3. this MD5 is automatically injected into the response (HTML, or
XML in
      Ajax XML based response).

It was not easy to get right. I have worked with Olivier Ramonat on
this part
as we wanted to have this kind to context into Vision2Pixels server.
At this
point we think it works just fine and that it is a very cool
technology.

> Of course, many do this error to see state at the server side (and you en=
d =A0
> up with errors and unexpected behaviors from the client point of view).

I think AWS Web_Block support is immune to that :)

Pascal.