From: <an...@io...> - 2005-07-04 16:37:29
|
Chris Winters wrote: > Hey, if FastCGI works better with CGI::Fast I'm all for switching. Are > there any other side effects? And is CGI::Fast the more commonly used > interface? (I've never used FastCGI in production, so it's all a shot > in the dark for me...) I haven't used it in production either.. I'm just running my development box under FastCGI now since I'm experiencing somekind of a memory consuming loop when I stop my apache when it has served an OI2 request under mod_perl (Which then causes wild swapping of _everything_). CGI::Fast seems to be older than FCGI and not updated in a while, but that doesn't necessarily make it outdated. Maybe the motivation behind FCGI has been jut to provide a version of FastCGI gateway which is independent of the CGI.pm module, which some people concider bloated. So pretty blind shots for me also, but for my use it seems that CGI::Fast works better. I haven't seen any side effects yet except that is fixes the post parameter problem. .. By the way I think CGI request doesn't mix url parameters with post parameters like Apache request does. They can be acquired from CGI object with url_param() just like post params are acquired using param(). It might be nice to add some kind of a separation for post and url params in OI2 also (I think this is already in JIRA by Teemu?) and make the behaviour consistent across different Requests. Maybe so that all the params are stuffed to $request->param but they are also ackquirable intependently with $request->url_param and $request->post_param ? - Antti |