Python equivalent of Perl-ISAPI?

[rurpy at yahoo.com]

rurpy at yahoo.com wrote:
> Atanas Banov wrote:
> > rurpy at yahoo.com wrote:
> > > Steve Holden wrote:
> > > > rurpy at yahoo.com wrote:
> > >
> > > > > Pure cgi is too slow.  "Active Scripting" means ASP, yes?
> > > > > I need something that will do cgi scripts (a lot of which I already
> > > > > have
> > > > > and can modify but don't want to rewrite extensively, partly because
> > > > > of time issues, partly because I want to preserve some degree of
> > > > > portability back to a unix environment.).   I want something that does
> > > > > for IIS what mod_python does for apache.  Fastcgi looked scary even
> > > > > on unix plaforms, seems like an act of desperation on Windows,
> > > > >
> > > > Yes, ASP is Active Scripting.
> > > >
> > > Except I need cgi, not asp, for the reasons i gave.
> >
> > it seems to me you have no clear idea what you need.
> >
> > you say you have a lot of CGIs written but you don't clarify if that is
> > Python or Perl. since you look for python intergration, it seems they
> > are in python, however in previous posting you say you'll have to
> > revert to Perl for solution. it just doesnt make sense! if you use
> > Perl, you will have to REWRITE the scripts and if you do so, it's
> > unclear why wouldnt you use a superior technology like PHP/ASP/JSP -
> > any of those is way easier to manage.
> >
> > it's also unclear why don't you use apache on windows, if mod_python is
> > your poison.
> >
> > here is how i imagine you have the layers:
> >    [scripts (CGI?)]
> >    [glue]
> >    [web server (IIS?)]
> >
> > where the discussion is about the "glue" between them. you say CGI is
> > too slow for you, so you will want something maintaining the CGI
> > programming model, but faster. this thing is called FastCGI - but you
> > are unhappy about it either. there is no way any perl "glue" can solve
> > your problem between your web server and your python scripts
> > whatsoever. you'll have to re-code the scripts for perl.
>
> The final solution must run in a Windows/IIS environment.
> Those are part of the requirements which I do not control.
> There is code in both Perl and Python.  I wrote the Python
> stuff and inherited the Perl stuff.  It is not web-based now
> but conversion to generate html output instead of text is
> probably straightforward.  Additional requirement is that
> is should be movable to unix without too much work.
> The layers are:
>
> [database] [equipment interface]
> [glue]
> [cgi]
> [webserver - IIS]
>
> As fo PHP/ASP/JSP?  I am doing all the work.  I know Perl
> and Python.  I don't know PHP/JSP.   (Also, JSP will require
> a lot of new Java infrastructure support, yes?)  As for ASP,
> I wonder about the "easily moved to unix" requirement.
> (I know apache has an asp module but I don't know if other
> web servers do, or how compatible apache's is, and I don't
> know if I have time to reliably answer those questions.)
> Why do you say PHP/JSP/ASP are superior technologies?
>
> All I want to do is avoid the cost of starting a new Python
> (or Perl) interpreter on each page request.  This is what
> I understand Perl-isapi and Perl-Ex does.  My question
> is simply if there is something similar for Python.
> I have concluded the answer is no but hope I'm wrong.

Din't find anything more and no further replies
here so here is a quick timing I did...
  Perl-Ex:        0.014 sec/page
  Perl-ISAPI:     0.168 sec/page
  Perl-cgi:       0.187 sec/page
  Python-cgi:     0.286 sec/page

I can't ignore the 20X better performance of
Perl-Ex vs Python, so I guess this is a loss
for Python and a win for Perl.