paulb@239 | 1 | Session Support in WebStack
|
paulb@239 | 2 | ---------------------------
|
paulb@239 | 3 |
|
paulb@239 | 4 | Various frameworks do not support sessions. In order to provide primitive
|
paulb@239 | 5 | support for sessions within WebStack upon such frameworks, the
|
paulb@239 | 6 | WebStack.Helpers.Session module is used to provide a simple file-based session
|
paulb@239 | 7 | store. It is necessary to create a directory called WebStack-sessions in a
|
paulb@239 | 8 | particular location for the session store to function, and the location depends
|
paulb@239 | 9 | on the framework as summarised in the following table.
|
paulb@239 | 10 |
|
paulb@239 | 11 | Framework Location
|
paulb@239 | 12 | --------- --------
|
paulb@239 | 13 | BaseHTTPRequestHandler The directory where the server is run.
|
paulb@239 | 14 | CGI The directory where the handler resides.
|
paulb@239 | 15 | mod_python The server root (eg. /usr/local/apache2).
|
paulb@243 | 16 | Twisted The directory where the server is run.
|
paulb@239 | 17 |
|
paulb@239 | 18 | Note that the WebStack-sessions directory must have the appropriate ownership
|
paulb@239 | 19 | and privileges necessary for the server/framework to write session files into
|
paulb@239 | 20 | it.
|
paulb@281 | 21 |
|
paulb@281 | 22 | Unsupported Frameworks and Framework Issues
|
paulb@281 | 23 | -------------------------------------------
|
paulb@281 | 24 |
|
paulb@281 | 25 | Webware 0.8.1 has problems creating sessions and is therefore not supported.
|
paulb@281 | 26 | Webware releases later than 0.8.1 (at least until the 2004-02-06 CVS snapshot
|
paulb@281 | 27 | used for testing) do not support session detection or expiry correctly.
|