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,FREEMAIL_FROM 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!news4.google.com!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: Annoucing memcache-ada 0.1 Date: Mon, 17 Jan 2011 12:07:30 +0100 Organization: Ada @ Home Message-ID: References: <4d335a76$0$43992$742ec2ed@news.sonic.net> <2b5cd851-c148-41f4-95e7-14f235846e6a@q18g2000vbk.googlegroups.com> NNTP-Posting-Host: h+uYBkNaz9IXrK6m/ApHiQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 User-Agent: Opera Mail/11.00 (Win32) Xref: g2news2.google.com comp.lang.ada:17454 Date: 2011-01-17T12:07:30+01:00 List-Id: Le Mon, 17 Jan 2011 11:40:12 +0100, Simon Wright a = = =C3=A9crit: > 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 depen= ds = on the involved functionality. If you are serving pages whose access = requires some right (like browsing a private forum), then it just requir= es = 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 th= at = 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). So this depends on what kind of process is involved. -- = Si les chats miaulent et font autant de vocalises bizarres, c=E2=80=99es= t pas pour = les chiens. =E2=80=9CI am fluent in ASCII=E2=80=9D [Warren 2010]