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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,469b2bba5f3a7bd
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.202.37 with SMTP id kf5mr2262293pbc.7.1334333370347;
        Fri, 13 Apr 2012 09:09:30 -0700 (PDT)
Path: 
 r9ni52060pbh.0!nntp.google.com!news1.google.com!goblin1!goblin3!goblin.stu.neva.ru!gegeweb.org!feeder.news.orange.fr!not-for-mail
Date: Fri, 13 Apr 2012 18:09:29 +0200
From: Pascal Obry <pascal@obry.net>
Organization: Home - http://www.obry.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr-FR;
 rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: [OT] Re: New AWS-based website
References: 
 <76df311e-7bac-4326-bf21-b611c701ebeb@do4g2000vbb.googlegroups.com>
 <4f868816$0$282$14726298@news.sunsite.dk>
 <6ea96041-f949-421b-a76e-05ada890ec77@z17g2000yqf.googlegroups.com>
 <4f86e680$0$294$14726298@news.sunsite.dk>
 <9114785.555.1334260823562.JavaMail.geo-discussion-forums@ynmf4>
 <87aa2gcaks.fsf_-_@adaheads.sparre-andersen.dk>
In-Reply-To: <87aa2gcaks.fsf_-_@adaheads.sparre-andersen.dk>
Message-ID: <4f884fb9$0$21475$ba4acef3@reader.news.orange.fr>
NNTP-Posting-Date: 13 Apr 2012 18:09:29 CEST
NNTP-Posting-Host: 82.124.198.12
X-Trace: 1334333369 reader.news.orange.fr 21475 82.124.198.12:6322
X-Complaints-To: abuse@orange.fr
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Date: 2012-04-13T18:09:29+02:00
List-Id: <comp.lang.ada>


Jacob,

> And now that you've got me started; why to most web developers insist on
> keeping the details of my state hidden inside their system, instead of
> storing the state in cookies?  (It would avoid the whole mess of
> sessions timing out for no apparent reason.  And it would allow the more
> adventurous visitors to adjust the state as needed.)

Because cookies are limited in size and are sent with every request. So
to save bandwidth it is far far better to not use cookie for session
management. It is better to use them as id management and then store the
session data into an internal structure in the server.

BTW, using the Web Block support in AWS it is quite easy to build
complex templeted system with Ajax with an elegant session named
context. Give it a try!

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B