More perlish would be:
insert_head => unshift
insert_tail => push
Although these method-names are perfect.
next($b) => next()
prev($b) => prev()
I don't know whether my conception is right but $bb is something like an
iterator. Why does one have to pass $bb->next($b) $b, wouldn't
$bb->next() that
eos_create => create_eos would sound more like you would use it in a
human language although I'm also happy with eos_create.
flush_create => create_flush same as above
Tom
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette:
well is the "perl" really executing your perl or the one that comes with
the system?
# which perl
If you don't have uninstalled the default perl your command will execute
the system perl because its located into /usr/bin/perl. Where's your
personal built perl installed?
# perl -V
will tell you
Tom Schindl wrote:
More perlish would be:
insert_head => unshift
insert_tail => push
Although these method-names are perfect.
I should have mentioned that we want to stay as close as possible to the C API
and change things only when things aren't quite perlish (like when C passes
its arguments by
Tom Schindl wrote:
eos_create => create_eos would sound more like you would use it in a
human language although I'm also happy with eos_create.
flush_create => create_flush same as above
Both are a direct mapping to the C functions:
APR::Bucket
apr_bucket_eos_create(list)
APR::BucketAlloc lis
Hi Tom,
Thank you for your help.
I am not using the perl that came with the system. I compiled the source
code from scratch and using that.
I have not uninstalled the perl that came with the system, I compiled
the perl 5.8.3 in other path (/usr/local/apache)
and used that perl for compiling and b
Ok. I have no idea of the C-API so things should be fine.
Tom
Stas Bekman wrote:
Tom Schindl wrote:
More perlish would be:
insert_head => unshift
insert_tail => push
Although these method-names are perfect.
I should have mentioned that we want to stay as close as possible to the
C API and change
Hi!
I'm interested in not letting coding mistakes crash the server, or at
least not eat all the RAM and CPU. Perry answered this
(http://marc.theaimsgroup.com/?l=apache-modperl&m=100162037703860&w=2) but
that is for use with mp1, what could you do with mp2?
Kind Regards,
Stefan Cars
--
Report
On Wed, 26 May 2004, Stas Bekman wrote:
> Date: Wed, 26 May 2004 19:08:40 -0700
> From: Stas Bekman <[EMAIL PROTECTED]>
> To: Jie Gao <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [mp2] 1.99_14: socket problem
>
> Jie Gao wrote:
> [...]
> If you've moved to Apache 2.0.49, it no
On Fri, 2004-05-28 at 02:51, Tom Schindl wrote:
> As Perrin already said Apache::DBI or once more a Singleton-Class
> providing the DBH, although I'd use Apache::DBI because it handles
> everthing for you.
I typically use them together. Apache::DBI handles the persistence, and
the singleton pro
On Fri, 2004-05-28 at 05:07, Bheema Rao Merugu, BSC, Ambattur, Chennai
wrote:
> I am not using the perl that came with the system. I compiled the source
> code from scratch and using that.
It looks to me like you have a file permissions problem. Running from
mod_perl you are probably operating as
On Thu, 2004-05-27 at 22:32, [EMAIL PROTECTED] wrote:
> Somebody told me that if i use the data type "bytea" for my images
> in postgresql it could be very heavy in the web, does mod_perl
> have a good solution for that?
If what you mean is that you plan to serve images out of your database,
then
On Fri, May 28, 2004 at 02:37:39PM +0530, Bheema Rao Merugu, BSC, Ambattur, Chennai
wrote:
> Hi Tom,
>
> Thank you for your help.
>
> I am not using the perl that came with the system. I compiled the source
> code from scratch and using that.
Ok, I think what people meant to suggest was this:
Hi,
I'm wondering if anyone has any advice about how to overcome the
following problem. My setup is:
Apache/2.0.49 (Unix) mod_perl/1.99_14 Perl/v5.8.4 mod_ssl/2.0.49
OpenSSL/0.9.7d PHP/4.3.6
on a Solaris 8 box.
In my apache error log I have warnings containing the string:
Can't locate object m
Stefan Cars wrote:
Hi!
I'm interested in not letting coding mistakes crash the server, or at
least not eat all the RAM and CPU. Perry answered this
(http://marc.theaimsgroup.com/?l=apache-modperl&m=100162037703860&w=2) but
that is for use with mp1, what could you do with mp2?
Assuming that you are
David W Smith wrote:
[...]
In my apache error log I have warnings containing the string:
Can't locate object method "user" via package "Apache::Connection" at
/usr/local/lib/perl5/site_perl/5.8.3/Apache/AuthenIMAP.pm line 70.\n
[...]
When I run:
perl -MApache2 -MModPerl::MethodLookup -e print_metho
On Thu, 2004-05-27 at 21:34, Mike Blazer wrote:
> It's hard to extract the part of the code because my configs look wild
> :)
Holy cow, this is a lot of code. The simplest thing I can think of to
see what's going on is to turn on Apache::DBI debugging and then watch
your error_log. If you see a
On Fri, 2004-05-28 at 14:02, Stas Bekman wrote:
> Assuming that you are using prefork mpm, all the answers Perrin gave apply to
> mp2. But those tools need to be ported. I remember Perrin was planning to port
> Apache::SizeLimit, I'm not sure if he did.
Not yet, but as you say, it's pretty quick
Jie Gao wrote:
On Wed, 26 May 2004, Stas Bekman wrote:
Date: Wed, 26 May 2004 19:08:40 -0700
From: Stas Bekman <[EMAIL PROTECTED]>
To: Jie Gao <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: [mp2] 1.99_14: socket problem
Jie Gao wrote:
[...]
If you've moved to Apache 2.0.49, it now gives y
On Wed, 2004-04-28 at 15:38, Perrin Harkins wrote:
> On Wed, 2004-04-28 at 15:34, Tyler Rorabaugh wrote:
> > I need object persistance between servers
> > Say for example you had a person object
> > That container first / last name
> > I want the object to contain the same data for each session
> >
Ok, I am not interestd in relying on globals like I was, but I did stuble
on esomething, and after reading the documentation, I am a bit confused as
to what I did.
I wanted to be able to get access to:
my $r = Apache->request;
inside two different modules and the error log told me to turn
Perrin Harkins wrote:
> You could still be foiling it
> by stashing database handles in globals or closures though.
Thanks a lot, Perrin, in fact this helped a lot. You convinced me that
it's my error :)
The idea that one db handle is being inherited by the forked childs
helped. I finally found
On Fri, 28 May 2004, Stas Bekman wrote:
> Date: Fri, 28 May 2004 11:27:46 -0700
> From: Stas Bekman <[EMAIL PROTECTED]>
> To: Jie Gao <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [mp2] 1.99_14: socket problem
>
> Jie Gao wrote:
> >
> >
> > On Wed, 26 May 2004, Stas Bekman wrote:
>
Jie Gao wrote:
[...]
Thanks very much. I'll do when I find some time for it. Right now I'm getting
segmentation faults and am going to debug it today.
Sure, please take your time.
BTW, I am getting this in the log:
Undefined subroutine &Apache::Connection::AUTOLOAD called.\n,
It seems that some mod
Nathanial P. Hendler wrote:
[...]
What does GlobalRequest do
exactly, and is there a better way to get Apache->request in modules?
http://perl.apache.org/docs/2.0/user/config/config.html#C_GlobalRequest_
--
__
Stas BekmanJA
Jie Gao wrote:
Oh, wait, it was an error, not a warning. You want:
$SIG{__DIE__} = \&Carp::confess;
then.
OK, I've got this after changing to use confess:
[Sat May 29 10:53:41 2004] [error] [client 129.78.64.21] Undefined subroutine
&Apache::Connection::AUTOLOAD
called at /usr/local/perl-5.8.4/
On Fri, 28 May 2004, Stas Bekman wrote:
> Date: Fri, 28 May 2004 17:36:44 -0700
> From: Stas Bekman <[EMAIL PROTECTED]>
> To: Jie Gao <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [mp2] 1.99_14: socket problem
>
> Jie Gao wrote:
> [...]
> > Thanks very much. I'll do when I find som
Yes, I'd read that section several times before posting. I understand
that the setting is enabled at some points, disabled at others, and can be
enabled. I don't have an old version if CGI.pm, and I don't understand
what that has to do with anything. It seems to do more than just setup
the glob
Nathanial P. Hendler wrote:
Yes, I'd read that section several times before posting. I understand
that the setting is enabled at some points, disabled at others, and can be
enabled. I don't have an old version if CGI.pm, and I don't understand
what that has to do with anything. It seems to do mo
0.05 2004-05-29
- The handler method was broken.
- Added a warning about being careful to make sure that the app object
goes out of scope at the end of the request, because if you make it a
global via the Mason Interp object's set_global() method, it can
persist across requests.
-dave
/*
30 matches
Mail list logo
