-- ZacharyBennett - 2012-03-02

The following components in the Architecture I've named for the sake of a Session Management point of view:

Browser - What the user is working with

Display Engine - The Java Program that is driving the diaplay in the broswer by controlling the conversion between session state information and the necessary HTML/CSS to render it

Session Manager - The Java Program that is managing the communication between the Display Engine, the MySQL database and JESS in order to keep all components properly informed of the current session state

Current State Manager - The Jess system that is driving the dependencies and updating the session state as dependencies change and are fulfilled in order to maintain an up to date session state

Session State Repository - This is the MySQL database that holds all the long-term information, test scores, username and password pairs and further information necessary to save and restore inactive session states

Topic attachments
I Attachment Action Size Date Who Comment
Pngpng SuccessfulSessionResume.png manage 31.7 K 2012-03-06 - 20:09 ZacharyBennett  
Pngpng WorksheetDisplayProcess.png manage 39.6 K 2012-03-06 - 20:11 ZacharyBennett  
Topic revision: r3 - 2012-05-21 - JimSkon
 
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback