[AWS] AWS - maintain state between server and client

Thomas Løcke thomas.granvej6 at gmail.com
Thu Apr 8 16:10:17 CEST 2010


On Thu, Apr 8, 2010 at 3:52 PM, Pascal Obry <pascal at obry.net> wrote:
> Indeed not direct cookie support. No need to mess with cookie as AWS will
> do that for you. AWS send a cookie behind the scene to record a session
> with the web browser. At the application level the session variables are
> stored into a key/value table. See AWS.Sessions. See the callback
> in demos/multiple_session.adb for a simple counter.


Yes, but this session cookie is expired at the end of the session,
making it badly suited for my needs, where state needs to be kept
*between* sessions, ie. I need "ordinary" cookies, where the expire
attribute can be set.


> No. But not needed as the necessary feature is provided by a higher level
> API. Note that it is still possible to mess with cookies by sending specific
> headers. But this is not encouraged.


Why is this not encouraged? And if it isn't encouraged to mess with
specific headers, then why not make available a nice api for generic
cookie management?  :o)


> Thanks for the nice words.

You're welcome.


> When you are familiar with the basic AWS API may I suggest that you have
> a look at the Web_Block support. With this it is possible to componentize
> a Web application. This is used in the Vision2Pixels image critics Web
> application. You can see the sources here:
>
>   http://git.savannah.gnu.org/cgit/v2p.git/


I will do that. Thanks for the info.

Thomas Løcke


More information about the AWS mailing list