Work In Progress

Requirements

• Identify and evaluate PHP session persistence mechanisms
• Unified approach to session management
  • Session Lifecycle
  • Session Access/API
  • Session/Client Relationship (keys)
  • Session Scope
  • Session Management
• Control Panel view of sessions
• Web tier needs a handle to social sessions
• Social tier needs a handle to multiple api sessions

Deliverables:

• Documentation of session lifecycle

Bill's Notes
 

Web Tier holds a social session
The social session needs to hold on to multiple API sessions

Notes from Session Discussion

Login in the social tier (Possibly Move?)
Encapsulate all sessions in classes
A social session is a network's connection on behalf of a user.
Consistent model for how sessions are established and maintained.
Session Life-cycle
Session Access
Never do $_SESSION, session service provides you with a session.
Social session contains API keys.
Session Client Relationship
Limited Sessions for Widgets

Session Life-cycle document - how do they work in each tier.
Here is how keys to sessions are passed around.
Associating network ID/Scope of sessions

Session
Life cycle
Access/API
Scope
Management

 
1. Session Manager: Wrap Session Management for Tracking
2. Session Life-cycle
3. Wrappers: Wrap Session Types in Classes (Model Across social sessions)
4. New Session Type Support
4. Control Panel Session Display
5. known persistence mechanisms Memchache/Database Backed
6. Life-cycle management existing project for this.
7. Must provide all management information itself, no direct DB access.

Investigate Open Authentication for Session Management)