| Jim Gallacher 2006-12-02, 1:13 am |
| Martin Stoufer wrote:
>
>
> Jim Gallacher wrote:
> Jim,
> I honestly didn't even think of this. As I started with v.3.2, my
> example would of ended up being rather myopic in scope. My suggestion
> for the time being is to split my page up into SubPages; one per
> version. Adding these disclaimers (or sanitized versions that don't
> disclose and secrets/non-finalized ideas) at the top will help alot.
> Since I don't have any examples from 3.1.4 or 3.3, I will put a call out
> to the list and see if anyone is willing to post some small examples.
I wouldn't create separate pages just yet. My guess is that your actual
code will be compatible across versions 3.1 to 3.3 as the session api
has not changed so your usage will be the same. Version >= 3.2 just
gives some flexibility in the session configuration through a bunch of
PythonOptions.
I think Graham's suggestion is best - avoid the problem all together by
not using "PythonOption session" in your configuration.  On the other
hand being able to set the session timeout and some other options in the
apache configuration is pretty handy so you might want to mention them.
I've appended the relevant 3.3 PythonOptions to bottom of the this email
for your reference.
Also, I wouldn't worry too much about 3.1.4 support. It's getting pretty
long in the tooth.
> As for how to deal with this issue at the wiki-wide level, I am very
> hesitant to promote a required style guide on pages that discuss topics
> that vary across releases. Those looking to post a quick nugget of
> valuable info won't if the process requires too much effort. It may well
> suffice by having a minimal requirement that posters say upfront what
> version(s) their examples/info is valid for.
Some sort of detailed style guide is likely not realistic, but I suspect
if new authors always see the same sort of boiler plate at the beginning
of each example they'll take the hint. Something simple like "Works with
version 3.x.x" may be sufficient. If someone comes along and tries it
with a different version it'll be easy enough for them to amend that to
"Works with version 3.1, 3.2".
Jim
Version 3.3 PythonOption reserved keywords
------------------------------------------
mod_python.legacy.importer * - Enables the obsolete importer.
mod_python.mutex_directory
mod_python.mutex_locks
mod_python.psp.cache_database_filename
mod_python.session.session_type
mod_python.session.cookie_name
mod_python.session.application_domain
mod_python.session.application_path
mod_python.session.database_directory
mod_python.dbm_session.database_filename
mod_python.dbm_session.database_directory
mod_python.file_session.enable_fast_cleanup
mod_python.file_session.verify_session_timeout
mod_python.file_session.cleanup_grace_period
mod_python.file_session.cleanup_time_limit
mod_python.file_session.database_directory
session - Deprecated, use mod_python.session.session_type
ApplicationPath -Deprecated, use mod_python.session.application_path
session_cookie_name - Deprecated, use mod_python.session.cookie_name
session_directory - Deprecated, use mod_python.session.session_directory
session_dbm - Deprecated, use mod_python.dbm_session.database_filename
session_cleanup_time_limit - Deprecated, use
mod_python.file_session.cleanup_time_limit
session_fast_cleanup - Deprecated, use
mod_python.file_session.enable_fast_cleanup
session_grace_period - Deprecated, use
mod_python.file_session.cleanup_grace_period
session_verify_cleanup - Deprecated, use
mod_python.file_session.cleanup_session_timeout
PSPDbmCache - Deprecated, use mod_python.psp.cache_database_filename
|