> -----Mensaje original-----
> De: Ged Haywood [mailto:[EMAIL PROTECTED]]
> Enviado el: miercoles, 16 de enero de 2002 23:30
> Para: Oscar Serrano
> CC: [EMAIL PROTECTED]
> Asunto: Re: weird problem. Lost of the POST data
Thank you Ged for your detailled information. I'm now debugging my scripts.
I'm still not sure if the problem is in the way I code, in CGI.pm or in the
Template Toolkit.
Thank you very much.
>
> Hi Oscar,
>
> On Wed, 16 Jan 2002, Oscar Serrano wrote:
>
> > So, one mod_perl CGi can cache several modules and several
> mod_perl cgis?
>
> It's not really a "mod_perl CGI", it's an Apache child process with
> its own built-in (persistent) Perl interpreter. In that sense it's an
> ordinary copy of the Perl interpreter which can load whatever Perl
> modules you have the memory for. The child sits around waiting for
> something to do. You give it something to do by handing a request to
> Apache (usually from a browser) which may or may not be configured to
> cause the Perl interpreter to do something with it. If it does
> something with the request it may change things inside the memory
> pages of that child's Perl interpreter which aren't changed in the
> interpreters of any of the other apache children.
>
> > Apache::Registry which I'm interested in.
>
> Apache::Registry provides the Apache+mod_perl process with an environment
> similar to what you see when you use mod_cgi in an ordinary (non-mod_perl)
> process. But it's only similar, it's not identical. There are all sorts
> of things (mentioned in the Guide) that you have to look out for, mostly
> because it's only similar and because the Perl interpreter is persistent.
> There are alternatives to Apache::Registry which might be better for you,
> but none provides an exact replica of the CGI environment.
>
> > So the maximum size the httpd can grow is the size of all modules and
> > mod_perl cgis cached in memory. Am I right?
>
> Not quite, there are reasons for example why the child might grow
> without bound. It's covered in the Guide in great detail, including
> methods of calculating the process sizes and ways of dealing with
> any processes which misbehave.
>
> > print "Content-type: text/html\nPragma: no-cache\n\n";
> > $query=new CGI;
> > $in=$query->Vars();
> >
> > Now I have everything in $in.
>
> To be sure of it, why not print everything in $in to the error_log or
> something like that? (There's a whole chapter on debugging techniques
> in the Guide. :)
>
> > 501 Apache Error?
>
> In a properly written program, the ideal would be that no request
> could cause a server error. I suspect that there's something wrong
> with the way your code handles the request or (less likely) there's
> something wrong with the build of the server.
>
> 73,
> Ged.
>
>
