s, though, but I think that tends to be issues
with other perl modules that have shared library components. If you
(or anyone else!) have specific failures or test cases you've seen,
though, I'll look 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.
- at least thats what Konqueror tells me.
>
> Is there a way to force a browser to set a new cookie on reload?
>
>
> Thanks,
>
> Nenad
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
adn't seen this
novel method, but it has a nice feel to it.
> To conclude, if you make all your checkings/validations only in debug
> 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
relationship
with it, instead of simply having several classes with no code level
relationship other than supporting the same method calls.
Chip
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
e perl's may optimize this
(right now, if I recall, it only optimizes in the case of
pseudohashes).
Sadly, you'll never really be able to get compile time type
verification in perl (at least, in perl as it stands today). Even the
above syntax is only a promise to perl for possible optimizations and
not a request for perl to enforce the type of whatever shift returns.
Chip
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
as two different users. Most
normal users don't want to do that, though :)
Chip
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
Foo;
my $cref = sub { my $data = shift; return 1 };
timethese(400, { 'method' => sub { return $meth->bar },
'closure' => sub { return $cref->() },
'pkgmethod' => sub { return Foo->bar }});
packag
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; al
attern -- data interfacing.
There are a number of solutions. I just hope whatever gets written is
present and future proof enough to not depend 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 anot
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
> I have responded to the message by beginning a requirements document.
> >
> >http://www.officevision.com/pub/HTML-Widget/
> >
> > Please read it and send me any comments.
--
Chip Turner [EMAIL PROTECTED]
RHN Web Engineer
ferring to this weakness, but I suspect
they are. Sadly, the book doesn't seem to offer a reference for the
claim 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.
an XML to plaintext spitter-outter (very
technical 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
ay, of the GPL, it is implicitly allowed (and maybe arguably
encouraged) to not necessarily 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
.
(There actually may be a FAQ somewhere that answers in more detail;
I'm not sure offhand.)
Chip
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
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
> >
ich packets.
With a large enough sleep in the modperl code, 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]
wo shell windows:
$ perl -MDBI -e 'my $dbh = DBI->connect("DBI:mysql:mysql", "yy", "xx");
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
it pays off, but it is
an intended effect.
You 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
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 "ne
needed, though costly, OO interface to
most system calls. What alternatives are there really besides
rewriting and breaking 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 [
verything for me. HTML should NOT be used for posting emails.
--
Chip Turner [EMAIL PROTECTED]
ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
cated perl.
Even compiled perl would suffer from this problem. 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
o get it back unless you can figure out what it is
waiting for.
Again, this is Linux advice, so it may or may not be applicable. But
maybe it will help you find the problem. Perhaps the 'lsof' command
will show you if it has a file open. Generally D means either a
kerne
ciently sophisticated
attacker could change your code and make it non-trial without a huge
amount of labor.
Chip
--
Chip Turner [EMAIL PROTECTED]
Programmer, ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
mod_perl and perl have shown themselves to be pretty good about
not 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 w
e higher level mechanism
with only slight amounts of magic :)
Like $[, Apache::DBI serves a purpose for backwards compatibility (in
this case old CGI scripts instead of odd perl4 scripts), but it
probably should be disdained in general use, at least once a suitable
replacement is avail
ut my /tmp partition
was full and Netscape didn't complain and just sat there. Grrr.)
Chip
--
Chip Turner [EMAIL PROTECTED]
Programmer, ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
you mention
(seeking on DATA etc).
Chip
--
Chip Turner [EMAIL PROTECTED]
Programmer, ZFx, Inc. www.zfx.com
PGP key available at wwwkeys.us.pgp.net
than
you ever wanted to know about Awk compatibility ;)
A minor note -- have you considered a module for your SMTP code
instead of hard-coding it? Net::SMTP should work. It handles all the
pesky RFC details as well. Plus chances are it'll end up being more
portable in the long run.
Chi
or Postgresql.
I think you'll continue to bang your head against a wall unless you
change your strategy; slurping 150meg 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 [
t there will be per-thread overhead. Plus, AFAIK, no Perl
distribution comes shipped with multiplicity, so we'll likely have to
require Perl recompilation before mod_perl compilation.
So... mod_perl will exist in 2.0. We just have a lot of work to do
first,
33 matches
Mail list logo
