Re: [ANNOUNCE] Apache Hello World Benchmarks v1.02

2003-03-15 Thread Gerald Richter 
> >
> > Yes, Embperl per default caches a "compiled" version of the
> > stylsheet in
> > memory.
> >
> > Gerald
> >
> > P.S. There are also options to cache the result of the xslt
> > transformation
> > or any itermediate steps
> >
>
> Oh - A way of making it even faster in the benchmarks?
>

Yes, that should be possible. I have to take a look at Joshs benchmark
setting, after 2.0b9 is out

Gerald


--
Gerald Richter ecos electronic communication services gmbh
IT-Securitylösungen * dynamische Webapplikationen * Consulting

Post:   Tulpenstrasse 5  D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED]  Voice:   +49 6133 939-122
WWW:http://www.ecos.de/  Fax: +49 6133 939-333
--
|
|   Besuchen Sie uns auf der CeBIT vom 12. - 19. März 2003
|   Messe Hannover * Halle 17 * Stand F 36
|   http://www.cebit.de/
|
+-

PerlSendHeader On

2003-03-15 Thread Bleicke Holm 
Hi,
I am quite desperately trying to get mod_perl working.
I continue to get returned the source-code. Searching the doc and faqs
it looks as if I should turn on PerlSendHeader. But that's already done!
Also ExecCGI should be activated for the location.
In summary: 
http://foot/cgi-bin/test.pl works
http://foot/cgi-perl/test.pl DOESN'T

Here's my VirtualHost section:

  User holm
  Group users
  ServerName foot
  LogLevel debug
  DocumentRoot /var/www/foot/httpdocs
  ServerAdmin [EMAIL PROTECTED]
  ErrorLog /var/log/apache/foot-error.log
  TransferLog /var/log/apache/foot-access.log
  Alias /cgi-bin/ /var/www/foot/cgi-bin/
  Alias /cgi-perl/ /var/www/foot/cgi-bin/
  PerlModule Apache::PerlRun
  
#deny from all
SetHandler perl-script
PerlHandler Apache::PerlRun
Options ExecCGI
PerlSendHeader On
  
  
SetHandler cgi-script
Options ExecCGI 
  
  AddType application/x-httpd-php .php
  php_admin_value open_basedir /var/www/foot/httpdocs/


Anyone can help me out with this???
Cheers,
Bleicke

Re: Does perl have Failover with Open Source Web Platforms?

2003-03-15 Thread Christian Brink 
> If a 30 second delay is acceptable, even round robin dns forms a type of
>  failover. If the first ip fails, the browser tries the second, etc.

This is incorrect. IE does support some aliveness checking
(http://www.geocities.com/tufansevim/dnsroundrobin.html) and will cycle
through A records till it gets a response, but this is not specification
and most dns resolvers and will not work for all clients.
(http://www.acmebw.com/askmrdns/archive.php?category=81&question=359).

Round Robin DNS should only be used in load sharing (it does not load
balance) scenario until most DNS resolvers handle DNS SRV records, which
will be the correct way for a DNS to provide failover.
(http://www.isc.org/ml-archives/bind-users/2000/09/msg00350.html)

LVS, as you mentioned, is an excellent solution. If you want to stay with
a DNS solution then one of the Dynamic DNS servers may fit the bill, but
your end up with other problems.
- the name server propagation time you'll have
- the problem of driving a lot of traffic to your DNS server because of
the low TTL's.
- DNS servers that don't honor TTL times that are too low - then giving
out that bad info to it's users

Christian Brink