>
> Well, it's going to be a pretty strange environment that doesn't have a
> database connection in every process.
Sure. And beware of connections that are returned to the pool without
being rollbacked, too - the app then deadlocks itself because it holds
locks in the database and doesn't know
> Sounds like you should have some more code in your finally
> blocks. :)
Well I don't quite like having to do that everywhere, especially in
code I did not write. In Perl I only need one of them using some
AUTOLOAD trickery :-).
--
Dominique QUATRAVAUX Ingénieur dével
> I have to rebuild my perl and go through the Configure
> process to tell it to ignore `hostname`, unless you
> know a trick for that, too!
Well, what about creating a custom shell script named "hostname",
turn it executable, and put it somewhere in your PATH ?
#!/bin/sh
echo "darkstar.frop.org
> This is a diverse list
> with many different levels of Internet experience represented, and one
> off-topic post is not a big enough problem to merit banning people.
(my 0.02 Euros...)
I have to say that beyond the technical competence of people on this
list (which is excellent), I'm very
> hi everybody
> Do someone know how to connect to a distant host with perl (via sftp) and
> copy file from the host ?
You could just launch the "sftp" command using system(), or better,
the IPC::Run module from CPAN that was discussed here some time ago. I
would be surprised to hear that there
>
> The cause of the problem was my perl code calling flush.pl and
> flushing STDOUT at a point prior to it printing the response headers.
> Under mp2, flushing STDOUT calls mpxs_output_flush in
> xs/Apache/RequestIO/Apache__RequestIO.h, which in turn calls
> ap_rflush, which triggers creation of
> Line 199 checks for Apache.pm and Apache::Status, thus:
>
> if ($INC('Apache.pm') and Apache->module('Apache::Status'));
>
> I have both Apache.pm and Apache::Status installed.
Yes but Apache::module (which called by
"Apache->module('Apache::Status')") is an XS function defined by
libperl.so
> How do I send a file asynchronously?
>
> The classic example is download sites. You click on the file you want and
> it generates a thankyou page for your browser and also sends the file.
>
> So what's the correct way to do this?
>
Use a refresh META tag on the thank-you page, that points
> >although it never happened to me i have to fight some rumours. Is
> >it true that you can kill the whole server, not just the script
> >if you do something wrong with mod_perl? (I doubt it)
>
> It depends on what "wrong thing" you do.
In fact the worse you can do is to kill one of the mod_p
> Hi All
>
> I know I can use $r->dir_config() to access parameter values
> set in the config file with PerlSetVar, but is it possible to
> access the value of generic Apache configuration directives?
This is described in the [EagleBook] (worth your money, IMHO),
and this particular chapter is av
> So I installed and compared. I preferred the syntax of Mason, the
> flexible way to build components, the caching ... it have to be
> said here that I choose Mason ...
I agree, the caching is very good and one gets up and running in no
time with Mason. However, I find it imposes too much of a
> > Does anyone know of a way that I can server the contents of an
> > .htaccess file dynamically?
> Make the .htacess file in question a FIFO, with a script on the
> backend that Does The Right Thing.
Whoops, you would loose big when two concurrent Apache processes
attempt to access the .htacce
> The usual objection I've heard to using form fields is the security
> risk of people changing hidden fields in ways unforseen before submitting
> the form back, or of other people finding confidential data hidden in form
> fields if the user walks away and leaves their browser open, or the web
>
>
> You've addressed the issue of someone submitting a form with altered fields
> to attack the server, and pointed out some more advantages, but I don't
> think you've addressed the issue of protecting the "hidden" cleartext data
> from others on the client side.
True. But to tackle these conce
> I suppose that controllers would use internal redirects to call the
> views, is there a way to pass Perl data this way?
For the project I work on (a WWW-enabled PKI), we simply use CGI-encoded
URLs. This way, we can do the controllers in Perl and the views in
PHP, which is great for security
15 matches
Mail list logo
