Re: slashdot php article

2004-12-22 Thread Stas Bekman
allan juul wrote:
Perrin Harkins wrote:
On Wed, 2004-12-22 at 07:56 +0100, allan juul wrote:
it would be cool if it somehow somehwhere were more visible for 
everybody. for instance, if ASF on the menu on http://apache.org/ had 
a big fat checked mark and the words Apache2 compatible next to 
Perl, Jakarta or which ever was compatible with Apache2 (obviously 
many of these menuitems are not httpd-
related)

PHP is just as compatible with apache 2 as mod_perl 2 is.  The threading
problems are in the libraries, which is where Perl's threading problems
are as well.

aha - hmm, if that's the case why aren't *we* worried about people 
upgrading to Apache2 like the PHP folks apparently are, as seen in the 
slashdot article ? IOW, whats the big difference in the mod_perl 
community making an upgrade suggestion versus PHP making a non-upgrade 
suggestion if PHP is just as compatible with apache 2 as mod_perl 2 is ?

[sorry for getting a bit off topic here, but i'm just getting a little 
bit worried that the PHP folks actually are right here]
They are right. But there is not much to worry about. Those problems 
aren't modperl ones, but mostly CPAN modules' ones. Once people will 
discover problems they will fix those. mod_perl2 is probably the first 
real product that will give a real test to CPAN modules under threads.

That's said I think there are a few problems to solve in modperl, but we 
will get there and fix those as soon as they are discovered, so again 
nothing to worry about.

--
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: slashdot php article

2004-12-22 Thread Perrin Harkins
On Wed, 2004-12-22 at 21:04 +0100, allan juul wrote:
 aha - hmm, if that's the case why aren't *we* worried about people 
 upgrading to Apache2 like the PHP folks apparently are, as seen in the 
 slashdot article ? IOW, whats the big difference in the mod_perl 
 community making an upgrade suggestion versus PHP making a non-upgrade 
 suggestion if PHP is just as compatible with apache 2 as mod_perl 2 is ?

There seems to be an assumption in the PHP community that Apache 2 means
running with threads.  This sort of makes sense because most of the
other interesting features of Apache 2 (filters, protocol handlers) are
not available to them from PHP.  We don't assume people will run with
threads, and will probably recommend people use prefork where possible.

- Perrin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]