Data persistence between requests

[BenjamenMeyer]

StackInABox is designed to only last for the length of a test. Loaded into StackInAWSGI that likely means that the data in a normal StackInABox model would be destroyed between requests or at a minimum not reliably retrieved. To handle this StackInAWSGI needs to be able to have a type of session that can be created using the admin functionality. The session maintains the StackInABox services for itself, and should keep all the data alive until the session is closed.

Note: Normally the session is the thread in a normal unit test scenario. Here we need to make it part of the WSGI scenario.

• [x] Session to manage a StackInABox instance
  • [x] create a Session object to manage sessions
  • [x] create a session
  • [x] remove a session
  • [x] keep the session alive between WSGI requests
• [x] Ability to create a StackInABox instance from scratch when creating a session
  • [x] instantiate a session-specific StackInABox instance
  • [x] instantiate the various StackInABoxServices for the session

[BenjamenMeyer]

PR #9 does most of this, but we need to confirm that the sessions remain alive between WSGI requests.

[BenjamenMeyer]

Data remains alive between calls and sessions are persistent but limited to supporting a single worker. Issue #15 is tracking that last bit.