ic object requests)?
Try sending a Content-Length: header. Without a content-length, Apache
can't do keep-alive. I haven't looked at the mod_perl code recently, but
I see no reason for it to explicitly turn off keep-alive on you.
-Rasmus
l.com, right?
perl.com is an O'Reilly site. They can use their trademark on their own
site.
-Rasmus
rge, who in turn are hosted themselves by VA linux.
SourceForge is also all done in PHP, which may not be appropriate for a
mod_perl site.
You might want to talk to Brian Behlendorf and collab.net about this. He
might be able to do something interesting for you.
-Rasmus
age Apache is giving you is boneheaded. To get a
real error message, do this:
edit the Apache src/Configure script. Down around line 2140 you will see
a line like:
if ./helpers/TestCompile sanity; then
change it to:
if ./helpers/TestCompile -v sanity; then
and try again. Now you should get a useful error message.
-Rasmus
al hosts.
Host headers were not part of the HTTP 1.0 spec, but they are still sent
by most browsers going back to Netscape 2.0 and IE3. The presence of such
a host header does not mean the browser is an HTTP/1.1 compliant browser.
-Rasmus
he extra
memory needed to have both active, I don't see any real problem.
-Rasmus
on the test server.
Strange. I don't see that here. I actually get better results when I run
ab from another machine across a quiet 100M LAN. You must have something
really funky going on. Massive collisions? Bad cable? Duplex problem?
-Rasmus
really complex and time-consuming scripts.
By the way, PHP 4 also works as a module in aolserver now (Zeus coming
soon). Would be interesting to see if PHP could beat aolserver's built-in
tcl engine.
One thing that might be interesting to see would be the peak memory and
cpu usage for each one. That would give some indication of scaleability
issues. I have no idea how PHP will fare here. ;) Some improvements
were made in PHP 4 in this respect though.
-Rasmus
would reduce your memory requirements a bit. Performance-wise
they really are quite similar. Choosing one over the other is more of a
personal preference thing.
-Rasmus
t to use PHP's own language.
Although PHP is specifically geared to be a web scripting language it
actually does work as a standalone language and can be put right alongside
perl in /usr/local/bin on your system. Plenty of people do this, although
personally I would rather use Perl for non-web stuff.
-Rasmus
> According to Rasmus Lerdorf:
>
> > > > Those introduce more complex problems.
> > >
> > > And they are, of course, inevitable with almost any templating
> > > system.
> >
> > You know, PHP was once just a templating system.
> [
er how many layers of templates we will have 5 years from now.
It's a slippery slope...
-Rasmus
depends on your OS and libc version. DSOs were broken up until
Apache-1.3.9 on any glibc-2.1.1 system.
-Rasmus
what? Anybody care/know to explain
> when this [DSO] would change for good? I could dig the info about DSO at
> apache.org, but it doesn't help...
As of Apache-1.3.9, Apache's DSO support really should be stable. I am
running a bunch of servers with the DSO version of the PHP module without
any problems.
-Rasmus
first look this should be possible.
Apache 2.0's architecture is such that this is possible and there are
going to be other protocols supported at some point.
-Rasmus
to just set an Apache Note from your
module and configure mod_log_config to write the log entry in whatever way
you need using the note you set.
-Rasmus
16 matches
Mail list logo
