Eric,
What we do with our PHP/mod_perl boxes is develop everything locally on
development servers and then export it all using rsync. We have six
servers in our cluster that we rsync to.
Basically, we store everything in a local CVS repository. When changes
are made on the local dev boxes and
On Thu, 6 Jun 2002 20:15:24 -0600, Rob Nagler [EMAIL PROTECTED] said:
(http://sourceforge.net/projects/poop/).
RN Great, another mailing list. :-) Thanks.
It is not just mailing list. Don't miss
http://poop.sourceforge.net/. It has nice review of most Perl OO
persistence modules.
--
Ilya
On Thu, 6 Jun 2002, Slava Bizyayev wrote:
I mean that Apache fixup handler is not right place to decide should we
use gzip encoding or not.
I'd prefer to address it the point where the web server administrator has to
fix the Accept-Encoding HTTP header, if one is incorrectly issued by
On Fri, 2002-06-07 at 03:15, Rob Nagler wrote:
Agreed. Perl is good at text manipulation. It is imiho superior to
XSLT in all spaces which XSLT claims to solve. Once you have an XML
parse tree in Perl, it's trivial to write a translator to any format
more correctly than XSLT. My favorite
Hi all,
On Fri, 7 Jun 2002, Valerio_Valdez Paolini wrote:
On Thu, 6 Jun 2002, Jeff wrote:
We can take the discussion off-line if the list feels it will be too OT.
No, please :)
Yes, please.
73,
Ged.
Hello,
I'm working on mod_perl project which has many different modules. One is
so-called 'main' modules which loads other when needed. Until now
everything worked just fine, but now one module just says that he doesn't
know the variable I've exported.
And interesting is, that when I comment
On Thu, Jun 06, 2002 at 08:15:24PM -0600, Rob Nagler wrote:
The issue here is not whether TT is a bad approach, but rather why the
syntax is not Perl.
One reason is that I like to have minimal syntax in the templates. One
argument often used is that non-programmer find it easier to say
Viljo Marrandi actually wrote:
my $r = shift;
use vars qw( $log );
$log = $r-log();
if ( $some_case eq 'true' ) {
use Sub::First qw( $log );
I haven't tested, but this doesn't look as a good idea.
I don't think your code does what you think it does
(or what you think it
List,
I have the task in my hands of creating a web mail application. Initial
thoughts lead me to think I would use an external popper to pop mail and
parse it into a database for retrieval by the modperl application. The only
problem here is that I must provide the implementation of the mail
The answer to the trick question is that the subroutine name in package
Sub::First is misspelled (missing a t).
However, I think I would provide the Apache::Log object as a parameter to
new() rather than twiddling with package vars to try to have it magically
updated by Exporter. For example:
Bill Moseley wrote:
My MVC efforts often fall apart in the C an M separation. My M parts end
up knowing too much about each other -- typically because of error
conditions e.g. data that's passed to an M that does not validate. And I
don't want to validate too much data in the C as the C
Ok, so continuing down the path of a single sign-on system, I've completed a
rough framework, and it works fine. However, I thought it might be nice to
segregate the various bits of information into different cookies.
Unfortunately, setting multiple cookies doesn't seem to be working. Here
are
On Fri, 7 Jun 2002, Ken Miller wrote:
Ok, so continuing down the path of a single sign-on system, I've completed a
rough framework, and it works fine. However, I thought it might be nice to
segregate the various bits of information into different cookies.
Unfortunately, setting multiple
On 6/7/02 1:04 PM, Perrin Harkins wrote:
For example, if you have a form for registering as a user which has
multiple fields, you want to be able to tell them everything that was
wrong with their input (zip code invalid, phone number invalid, etc.),
not just the first thing you encountered.
Hey Perrin Bill --
You could also just punt and push this out to the
controller. (Not very pure but simple to implement.)
This is exactly what I had in mind. (Perhaps you can explain what you mean
by not very pure.) The methods in any model module I would write would
have expectations
Hello,
is there a possibility to limit mod_perl users in the
same way as the PHP 'open_basedir' option does?
Quoting from the PHP manual:
---
open_basedir - Limit the files that can be opened by
PHP to the specified directory-tree.
When a script tries to open a file with, for example,
fopen
Yup, just confirmed it. 1.3.20 works fine, but .24 is busted.
I'll try the latest CVS version.
Thanks guys!
-klm.
-Original Message-
From: Balazs Rauznitz [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 07, 2002 2:48 PM
To: Dave Rolsky
Cc: Ken Miller; [EMAIL PROTECTED]
Subject:
::really hesitates to step into this ... but like a train wreck ... he
simply can't resist::
It's like asking why XML has different syntax and semantics from Perl.
Well, if you read the XSLT spec and then look at an XSLT program,
you'll see a lot of verbosity and a lot of general purpose
On Thu, Jun 06, 2002 at 05:08:56PM -0400, Sam Tregar wrote:
Suppose you have a model object for a concert which includes a date. On
one page, the designers want to dipslay the date in a verbose way with
the month spelled out, but on another they want it abbreviated and fixed
length so
::realizes this may be going a bit futher a field ... but tries to maintain
topicality::
Chris writes:
Perl handels Regex's better than C, this is one of the reasons people
use Perl.
I disagree. Perl's Regex processor is written in C. The difference is
that it has outgrown Henry
On Fri, Jun 07, 2002 at 09:14:25AM +0100, Tony Bowden wrote:
On Thu, Jun 06, 2002 at 05:08:56PM -0400, Sam Tregar wrote:
Suppose you have a model object for a concert which includes a date. On
one page, the designers want to dipslay the date in a verbose way with
the month spelled out,
21 matches
Mail list logo
