[albatross-users] Re: Albatross-users digest, Vol 1 #176 - 14 msgs

[Dave Cole]

>>>>> "Tim" == Tim Churches <tchur at optushome.com.au> writes:

>> The application and execution context cooperate to deal with the
>> session.  The execution context is where the session data is
>> created manipulated, but the application is usually responsible to
>> loading and saving the session.  This allows the application to
>> maintain a long lived connection with a server if necessary.
>> Remember that an execution context lives only long enough to
>> process a single browser request.

Tim> That para should be near the front of the manual if it isn't
Tim> already.

This is what I added at the end of the Guide to Building Applications
introduction (just before section 4.1):

    http://www.object-craft.com.au/projects/albatross/albatross/app-guide.html

In all Albatross applications there are two important objects that
determine how browser requests are processed; the application object,
and the execution context object.  The application is a potentially
long lived object that provides generic services for multiple browser
requests.  A new execution context is created to process each browser
request.

One of the things that the application and execution context do is
cooperate to provide session functionality.  The execution context is
the object where session data is created and manipulated, but the
application is usually responsible to loading and saving the session.
This allows the application to maintain a long lived connection with a
server if necessary.

- Dave

-- 
http://www.object-craft.com.au