Re: Check POP3 E-mail
From: A. Sinan Unur (1usa_at_llenroc.ude.invalid)
Date: 11/06/04
- Next message: Gunnar Hjalmarsson: "Re: Check POP3 E-mail"
- Previous message: A. Sinan Unur: "Re: matching all perldoc names but no more"
- In reply to: krakle: "Re: Check POP3 E-mail"
- Next in thread: krakle: "Re: Check POP3 E-mail"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 6 Nov 2004 16:35:33 GMT
krakle@visto.com (krakle) wrote in
news:237aaff8.0411060746.379320e@posting.google.com:
> "A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in message
> news:<Xns9598802954588asu1cornelledu@132.236.56.8>...
>> krakle@visto.com (krakle) wrote in
>> news:237aaff8.0411050643.56e045a0@posting.google.com:
>>
>> > arguement. mod_perl scripts stay in memory. Unless you reset the
>> > values of a variable at the beginning of the script or before that
>> > variable is used it may contain the previous users data...
>>
>> Your statement is full of half truths. If you don't write 'good'
>> programs, then bad things surely mya happen. However, I have quite a
>> few CGI scripts that are being run under mod_perl, and I have yet to
>> run into such an issue.
>>
>> Sinan.
>
> Then you don't use mod_perl much. See my example.
Your example is bad code.
It is true that you will have problems if you do:
my $q = CGI->new;
sub mysub {
my $value = $q->param('some_param');
...
}
you will have problem, but you should not be doing that kind of thing
anyway whether your script is running under mod_perl or not.
Sinan.
- Next message: Gunnar Hjalmarsson: "Re: Check POP3 E-mail"
- Previous message: A. Sinan Unur: "Re: matching all perldoc names but no more"
- In reply to: krakle: "Re: Check POP3 E-mail"
- Next in thread: krakle: "Re: Check POP3 E-mail"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
