[ http://issues.apache.org/jira/brows...244
1188 ]

Jim Gallacher commented on MODPYTHON-127:
-----------------------------------------

+1
Your suggestion is logical. Explicit is better than implict.

> Use namespace for mod_python PythonOption settings.
> ---------------------------------------------------
>
>                 Key: MODPYTHON-127
>                 URL: http://issues.apache.org/jira/browse/MODPYTHON-127
>             Project: mod_python
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.3
>            Reporter: Graham Dumpleton
>         Assigned To: Graham Dumpleton
>             Fix For: 3.3
>
>
> In the interests of avoiding name clashes, I want to push that where mod_p
ython uses its own PythonOption settings, that they use a namespace. For exa
mple:
>     PythonOption mod_python.session_cookie_name ...
>     PythonOption mod_python.ApplicationPath ...
>     PythonOption mod_python.session_dbm ...
>     PythonOption mod_python.session_fast_cleanup ...
>     etc ....
> If appropriate for mod_python, multiple levels of naming should be used. F
or example, "session_fast_cleanup" is actually related to FileSession, so pe
rhaps it should be:
>   PythonOption mod_python.Session.cookie_name ...
>   PythonOption mod_python.Session.application_path ...
>   PythonOption mod_python.DbmSession.database ...
>   PythonOption mod_python.FileSession.fast_cleanup ...
> Thus, class name is interjected as second level in name. Also would like t
o see final attribute name settle on lower case with underscore between dist
inct words.
> We can support old names in mod_python for the time being but should depre
cate them.
> Any third party package developers should be strongly encouraged to also p
ut any of their own PythonOption settings names in their own unique namespac
e.
> Mailing list thread where this was first proposed, and in case there were 
followups of interest, was:
>   http://www.modpython.org/pipermail/...ary/020213.html

[ Post a follow-up to this message ]