Thanks for the reply,
I think I can set them during the script. The question (I should have
been more clear) is do they have to be set prior to running the
script, as they are when set via SetEnv?
As for speed, I haven't had the chance to compare the two methods
and the subjective speed of a CGI request is not useful as a point of
comparison. My perception is that it's quite slow but I think this is a
busy server. It's in a virtual server environment so I can't find the
actual cpu usage, etc. for the entire system. :-( I'm going to see if I
can increase the debug options via the environment vars and get
more details on performance.
I haven't experimented with sessions yet. Gerald can give you a
definitive answer on that one.
On 24 May 00, at 12:54, Aaron Johnson wrote:
> Scott Chapman wrote:
>
> > I am using the old Apache 1.2.6 and it apparently doesn't recognize
> > SetEnv so I don't know how to change the environment variables in
> > my scripts (which are running as CGI, not EmbPerl). Is there a way
> > to do this?
> >
>
> Someone please step in if I am leading him astray since I have never run
> Emperl in CGI mode. Set the variables at the top of the script - i.e.
> $ENV{EMBPERL_LOG} = "/where/ever/it/is/embperl.log"
>
> I don't know if all the variables work the same under CGI as they do
> under mod_perl.
>
> What is the performance like when used CGI based vs. mod_perl?
> Do sessions work and if they do, do they work the same way?
--
Scott Chapman
Technical Support Specialist
Lund Performance Solutions
[EMAIL PROTECTED] or [EMAIL PROTECTED]
Phone: 541-926-3800 www.lund.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
