into it and see if it is something we can fix.
Cheers,
Chip
--
Chip Turner [EMAIL PROTECTED]
Red Hat, Inc.
Subject pretty much says it all. What are the requisite 5.8 compile
options, besudes ithreads, for proper functioning with either mod_perl
branch? Or ones that should be avoided?
Chip
--
Chip Turner [EMAIL PROTECTED]
Red Hat, Inc.
},
'closure' = sub { return $cref-() },
'pkgmethod' = sub { return Foo-bar }});
package Foo;
sub new {
return bless {}, shift;
}
sub bar {
my $self = shift;
my $data = shift;
return 1;
}
--
Chip Turner [EMAIL PROTECTED
:)
Chip
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
to enforce the type of whatever shift returns.
Chip
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
version it doesn't matter how fast or slow they are. I think what matters
here is the clearness of the code.
I agree 100%.
Chip
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
darren chamberlain [EMAIL PROTECTED] writes:
Chip Turner ([EMAIL PROTECTED]) said something to this effect on 05/23/2001:
If I could make a suggestion -- don't depend upon a CGI.pm interface
for form variables. Abstract it away. One option would be to use
closures:
I agree
on any particular
interface (such as CGI or libapreq), or at the very least made to
easily use others. You never know when someone else may have another
templating technology that has a different interface!
Cheers,
Chip
--
Chip Turner [EMAIL PROTECTED
Paul Lindner [EMAIL PROTECTED] writes:
On Thu, May 24, 2001 at 09:59:36AM -0400, Chip Turner wrote:
darren chamberlain [EMAIL PROTECTED] writes:
The nice thing about closures is they could hide any interface at all
behind them; all that is required is that the function that generates
it and send me any comments.
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
as to the specific md5 vulnderability. (Hey Doug, wanna shed
some light on that somewhat cryptic passage? :)
It's been a while, but I believe SHA1 has yet to have a weakness
found. md5 is probably secure enough for websites though.
Chip
--
Chip Turner [EMAIL PROTECTED
term) that would be suitable for an email version.
Just a thought.
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
detail;
I'm not sure offhand.)
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
y make all of your work Free.
Of course, it's much more preferable for people to release things into
the Open. :)
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
, it should come pretty
much in its own packet. This will pretty much give you complete
certainty on what the client receives and when the client receives it.
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
Dirk Lutzebaeck [EMAIL PROTECTED] writes:
Chip Turner writes:
You can always use the definitive test of tcpdump on the client
machine. Something like (on linux):
/usr/sbin/tcpdump -s 4096 -w packets.out src (host) and port 80
Then examine packets.out for what data
my $sth = $dbh-prepare("SELECT GET_LOCK(\"mysql\", 5)"); $sth-execute;
my ($lock) = $sth-fetchrow; print "lock: $lock\n"; sleep 10'
Hope this helps,
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
could try something like:
$r-print("@{[\$foo]}");
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
eaking those modules up, as has partially been done
with some Apache modules vs CGI.pm. I'm not aware of any similar
attacks on IO.
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
Tom Christiansen [EMAIL PROTECTED] writes:
IO provides a needed, though costly, OO interface to
most system calls.
Huh? No, it doesn't.
I stand corrected. OO interface to _many_ _I/O_ system calls.
Better, or do you object to the "needed" part?
Chip
--
C
.
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
. At least when you
compile to C or Java the parse tree doesn't follow you around :)
Chip
--
Chip Turner [EMAIL PROTECTED]
Programmer, ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
leaking memory, as has apache. IMO it's much, much more likely a
problem concerning Registry and impolite scripts that are misbehaving
and leaving parts of themselves around.
Have you tried correlating the memory surges with any page accesses?
That may help narrow down the culprit.
Goo
scripts), but it
probably should be disdained in general use, at least once a suitable
replacement is available. Now, who wants to write it? :)
Chip
--
Chip Turner [EMAIL PROTECTED]
Programmer, ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
eg of data at a time just isn't the
appropriate way to solve almost any problem. Just use DBI, you'll be
happier for it :)
Chip
--
Chip Turner [EMAIL PROTECTED]
Programmer, ZFx, Inc. www.zfx.com
PGP key
25 matches
Mail list logo
