[mod_python] Types of handlers in 3.3?

Graham Dumpleton graham.dumpleton at gmail.com
Sun Apr 15 17:51:36 EDT 2007


You may find the following worth reading:

  http://www.dscpl.com.au/wiki/ModPython/Articles/GettingModPythonWorking
  http://www.dscpl.com.au/wiki/ModPython/Articles/SetHandlerVersusAddHandler

It may help to answer some of the questions you have and also some you
don't yet have.

Graham

On 16/04/07, Jorey Bump <list at joreybump.com> wrote:
> Francisco Reyes wrote:
> > In the docs for 3.3 I see under the performance section:
> >
> > Standard CGI:            23 requests/s
> > Mod_python cgihandler:  385 requests/s
> > Mod_python publisher:   476 requests/s
> > Mod_python handler:    1203 requests/s
> >
> > What is the syntax to enable the "Mod_python handler"?
> >
> > AddHandler mod_python .py
> > PythonHandler mod_python.handler
> > PythonDebug On
> >
> > Didn't give me any errors when I did apachectl graceful but the sample
> > program I tried gave an error.
>
> There is no mod_python.handler
>
> > I have a sample working using the publisher handler.
> > AddHandler mod_python .py
> > PythonHandler mod_python.publisher
> > PythonDebug On
> >
> > Are "Mod_python handler" coded different from mod_python.publisher?
>
> It's just an example using a custom handler, demonstrating a theoretical
> maximum without the overhead of the other handlers. Note that in
> practice, custom handlers will gain overhead as features are added.
>
> > Is the "Mod_python handler" indicating the program itself as the handler?
> > I see in the documentation.
> >
> > AddHandler mod_python .py
> > PythonHandler mptest
> > PythonDebug On
> >
> > Where mptest is the program.
>
> It's a custom handler that you must write yourself to test mod_python.


More information about the Mod_python mailing list