Thanks everyone - seems like I should just stick to CGI during testing or till got more experience doing web dev using python. On Sep 4, 2004, at 9:10 AM, Martin Maney wrote: > On Sat, Sep 04, 2004 at 01:56:47PM +0300, Ksenia Marasanova wrote: > [attribution MIA] >>> MaxRequestsPerChild 1 >>> KeepAlive Off >>> [...] >>> I always use this trick while developing: speed is probably >>> comparable >>> to CGIs but you can keep the same handler and session manager you >>> will > > OTOH, that trick changes the behavior of the entire server. Since I > often do my development on the production machine (speaking of having > issues pop up, developing and deploying on hosts that have had some > subtle yet important config differences accrue is a *big* winner that > way), that's not an attractive option. > >>> use in production. These details may be not trasparently portable >>> between a CGI and a mod_python publishing environment. >> >> I wonder if there is a trick like this for SCGI? I avoid plain CGI >> while developing for the same reasons... > > Good point about that w.r.t. mod_python - IIRC it runs the script using > the user and group of the apache server, which makes some things > totally different. Which was one of the reasons I stopped trying to > use mod_python a long while ago... > > I haven't had any problems going back and forth between plain CGI and > fastCGI (other than a few differences in the driver stub, which I can't > call to mind becuase I haven't had to touch that stuff in ages); > presumably SCGI would be much the same. > > Executive summary: there are nine and ninety ways ... and every single > one of them is *right*... for some set of circumstances, and wrong for > others. :-) > > -- > I must say I find television very educational. > The minute somebody turns it on, > I go to the library and read a good book. -- Groucho Marx > > _______________________________________________ > Quixote-users mailing list > Quixote-users@mems-exchange.org > http://mail.mems-exchange.org/mailman/listinfo/quixote-users