Re: mod_perl2 & POST data

"neophenix@xxxxxxxxx" <neophenix@xxxxxxxxx> wrote:
xhoster@xxxxxxxxx wrote:

Do you need to be able handle multipart posts, or just the old
fashioned single-part ones? I seem to remember something that could
handle single- part posts, but I'll have to go digging to find it
again.

This would just be for single-part posts.

It turns out that what I was thinking of us was just a way to run
cgi-like scripts without a web server. The perl script itself acts like
a web server, but it still uses CGI.pm to do the request parsing (but
doing it that way only doesn't work with multi-part post, so that part
of my memory was correct.)



Are you relying on heresay and/or irrelevant tests, or have you tested
it under your conditions (mod_perl2) and found it to be a hog? If so,
can you describe your tests?

To be honest I am just going by what I was told by others here and what
they have seen under normal cgi-bin use. The main issue is, if we are
only loading up 1 use of these scripts on each server and as such only
loading up CGI.pm once, then that is fine. However we need to load up,
say 400 copies of our index file on each machine, and each one would
then need CGI.

You kind of lost me about loading up index files. But anyway, if one uses
the normal mod_perl (Apache::Registry) method and use it with 500 scripts,
they all share the same image of CGI.pm---they are not loading it 500
times. I would be very surprised if the "normal" method of using mod_perl2
(ModPerl::Registry, I think) was any different in that regard.

We were told, and have read that each uri loads up the
packages it needs into memory, so I was led to believe that loading up
some 400 instances of a module like CGI would be a bit much.

With FastCGI and such that may be the case, but with Registry it should not
be. More of an issue would be having the non-CGI.pm portion of all those
scripts in memory. You should extract as much code that is in common
between them into your own custom *.pm, that way *that* code can be shared
amongst all of them, too.

Xho

--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
.

Relevant Pages

  • Re: mod_perl2 & POST data
    ... Do you need to be able handle multipart posts, ... This would just be for single-part posts. ... loading up CGI.pm once, then that is fine. ... some 400 instances of a module like CGI would be a bit much. ...
    (comp.lang.perl.modules)
  • Re: Repairing Permissions in Leopard
    ... the system left all night in sleep mode, ... mode, the running of the scripts wakes the system, runs them, then ... Please send all responses to the relevant news group. ... read posts from Google Groups. ...
    (comp.sys.mac.apps)
  • Re: mod_perl2 & POST data
    ... the normal mod_perl method and use it with 500 scripts, ... so I was led to believe that loading up ... code is in custom modules, the index files really just use them after ... then CGI is the way we will more than likely go. ...
    (comp.lang.perl.modules)
  • Re: script to check file size before sending
    ... >>I have looked through the posts and found several scripts, ... I would like to run a script against the file first to see ...
    (comp.unix.shell)
  • Re: agpgart
    ... disrespect while they can't even answer to my posts. ... FATAL: Module agpgart not found ... Then you can see if loading or not loading it makes any ... It has nothing to do with physical SCSI hardware. ...
    (alt.os.linux)