Apache Mod-Python - Commented: (MODPYTHON-28) Add a standard test handler in the distribution

This is Interesting: Free IT Magazines  
Home > Archive > Apache Mod-Python > May 2005 > Commented: (MODPYTHON-28) Add a standard test handler in the distribution





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Commented: (MODPYTHON-28) Add a standard test handler in the distribution
Jim Gallacher (JIRA)

2005-05-28, 5:45 pm

[ http://issues.apache.org/jira/brows...ts#action_66505 ]

Jim Gallacher commented on MODPYTHON-28:
----------------------------------------

You got the LaTex mostly right. There is one error (a stray backslash) which I've corrected in the attached patch.

As for the testing documentation itself, in section 2.4 item 7 you mention the need to "use a higher level handler such as mod_python publisher (see 3.1), mpservlets or Vampire". It may not be obvious to the reader that mpservlets and Vampire are not incl
uded with mod_python.

Maybe add somthing at the end of section 2.4 such:

\begin{seealso}
\seeurl{http://home.comcast.net/~d.popowich/mpservlets}{mpservlets}
\seeurl{http://www.dscpl.com.au/projects/vampire}{Vampire}
\end{seealso}

> Add a standard test handler in the distribution
> -----------------------------------------------
>
> Key: MODPYTHON-28
> URL: http://issues.apache.org/jira/browse/MODPYTHON-28
> Project: mod_python
> Type: Improvement
> Versions: 3.1.4, 2.7.10
> Reporter: Nicolas Lehuen
> Assignee: Nicolas Lehuen
> Fix For: 3.2.0
> Attachments: modpython2.tex-jg20050528-1.diff
>
> Improving the testing phase of the installation is crucial as we get a steady stream of question from new users who can't run the mptest or are confused about its meaning (for example, the fact that any URL ending with .py runs the mptest handler is mis

leading at first).
> We should include a standard mptest handler in the distribution so that we can better help beginners, without making them struggle with a new file PYTHONPATH, syntax errors in the handler, etc. Ideally, the mptest handler should display useful informati

ons both in the Apache log and in the result page ; this would help us check their environment and provide better help.
> The information displayed could be (both in the log and the result page) :
> - Apache version (+MPM type if this information can be queried at runtime)
> - Python version
> - mod_python version
> - sys.path
> - mod_python.publisher available yes/no
> - mod_python.psp available yes/no
> Of course, if anything goes wrong, it should be clearly stated in the Apache log (no misleading 404 errors, please !).
> The testing phase of the installation would then be : 1) set "SetHandler mod_python.mptest" directive and 2) watch the results. This would be far less messy as it is currently.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com