On 7/6/07, CraigT <[EMAIL PROTECTED]> wrote:
In this regard though, I would
like to ask what you recommend to pass back several paramters from a sub
The usual way to do it is to accept a list of return values:
my ($foo, $bar) = sub_call($param);
I'd like to focus on this problem here because
I realize that I have some redoing to do in relation to the scope/closure
stuff to make the PerlRun/mod_perl transition, and thanks to you all I have
a pretty good idea of what I have to do. In this regard though, I would
like to ask what you recommend to pass back several paramters from a sub
(
On 7/6/07, Christiaan Kras <[EMAIL PROTECTED]> wrote:
I'm 100% sure it happens in the modules that use lazy loading
(eval(require "module.pm")). Somehow @INC gets reset.
Are you sure @INC is getting reset? Sometimes people have this
problem because the user that apache runs as (usually "nobody
Hi,
My webhost allows me to use mod_perl (Apache 2 server by the way, Fedora
distro). And I'm glad I can because it speeds up my perl scripts a lot.
I've created a website that's based on CGI::Application,
Template-Toolkit and DBIx::Class. All works fine.
Those modules, including my own, are
On 7/6/07, CraigT <[EMAIL PROTECTED]> wrote:
Am I passing the paramters in the anchor
examples I presented earlier as I should using PerlRun or mod_perl?
I don't think you ever showed us the code. You just showed the code
where you print the HTML. If you can show us a complete sub and how
you
On 7/5/07, CraigT <[EMAIL PROTECTED]> wrote:
Is what I'm hearing you say is that in the PerlRun environment (and I'm
guessing the mod_perl environment too), anything that a subroutine uses
coming from outside that code must be passed as a parameter like
'&sub($paramter)'. Am I correct in this.
On 7/5/07, Todd Finney <[EMAIL PROTECTED]> wrote:
With due respect, Perrin, I disagree with the (common, unfortunately)
belief that a lack of an active release cycle indicates that a package is
somehow unsuitable. Sometimes, that just means that it's done.
Sure, but the real problem is that no
On 7/6/07, Frank Wiles <[EMAIL PROTECTED]> wrote:
Another option for this is to use MogileFS
(http://www.danga.com/mogilefs/) to store your files. You can
control the redundancy at the app level and it just "figures"
out where the file is when you request it.
Keep in mind, you have to
On Fri, 06 Jul 2007 11:15:25 -0700
[EMAIL PROTECTED] wrote:
Please keep your replies to the list so everyone can benefit.
> My install was sent with apache 1.x and so I've stayed with 1.x
> rather than upgrade to 2.x. Apache 1.x requires mod_perl 1.3.
Yeah, but there is no real reason yo
On Thu, 05 Jul 2007 10:46:51 -0700
[EMAIL PROTECTED] wrote:
> I'm trying to build mod_perl (1.30) into httpd (1.3.37) on Mac OS
> 10.3. However, the default make process does not build httpd with
> mod_so. The httpd (1.3.30) that came with the original installation
> does. So its a bit surprising
On Tue, 3 Jul 2007 10:26:55 -0400
"Perrin Harkins" <[EMAIL PROTECTED]> wrote:
> > 2) Store your upload in a shared partition (eg on a SAN, NFS,
> >iSCSI/OCFS2)
>
> That's ok if you need them on every server. Many applications just
> upload a file and process it on one server, so they don't n
A few more questions please. Am I passing the paramters in the anchor
examples I presented earlier as I should using PerlRun or mod_perl? Should
I be able to see the correct passed parameters when I pull them across to
the module invoked by the anchor prior to entering a sub in that module (my
12 matches
Mail list logo
