On Tue, Oct 29, 2002 at 11:27:51AM +0100, Derick Rethans wrote:
Ah yes - but that will contradict greatly, to the best version yet marketing
trick the Apache Group is advertising on their front page.
We can mention it to users, in the bug db etc. But officially documenting, that
Apache 2
The aspect people complaining about is more a version thingie, e.g.
they try to set up php 4.2.3 with apache 2.0.43 and this could not
succeed. Is it really necessary to document that apache 2.03x works
only with php 4.2.x1, php4.2.x2 and apache 2.04x only with php4.2y1
or php4.2.y2? It
At 08:43 29-10-2002, Gabor Hojtsy wrote:
The aspect people complaining about is more a version thingie, e.g.
they try to set up php 4.2.3 with apache 2.0.43 and this could not
succeed. Is it really necessary to document that apache 2.03x works
only with php 4.2.x1, php4.2.x2 and apache 2.04x
On Tue, 29 Oct 2002, Melvyn Sopacua wrote:
At 08:43 29-10-2002, Gabor Hojtsy wrote:
I think, it would be nice to add information to one place, the documentation
about Apache 2 support.
1. It's not production ready
Ah yes - but that will contradict greatly, to the best version yet
Hallo Melvyn,
Tuesday, October 29, 2002, 9:55:31 AM, you wrote:
At 08:43 29-10-2002, Gabor Hojtsy wrote:
The aspect people complaining about is more a version thingie, e.g.
they try to set up php 4.2.3 with apache 2.0.43 and this could not
succeed. Is it really necessary to document
At 11:30 10/29/2002 +0100, Friedhelm Betz wrote:
I think, it would be nice to add information to one place, the
documentation
about Apache 2 support.
1. It's not production ready
Ah yes - but that will contradict greatly, to the best version yet
marketing
trick the Apache Group is
1. It's not production ready
Ah yes - but that will contradict greatly, to the best version yet
marketing
trick the Apache Group is advertising on their front page.
We can mention it to users, in the bug db etc. But officially documenting,
that
Apache 2 is really a beta product, doesn't
Derick Rethans writes:
On Tue, 29 Oct 2002, Gabor Hojtsy wrote:
As far as I can see, we should not not put into the PHP
documentation
that Apache 2 is not production ready, but PHP is not
production ready
for Apache 2.
But it's incorrect :). By saying Do not use Apache 2 and PHP
As far as I can see, we should not not put into the PHP
documentation
that Apache 2 is not production ready, but PHP is not
production ready
for Apache 2.
But it's incorrect :). By saying Do not use Apache 2 and PHP in a
production environment you don't blame any of the
I think, it would be nice to add information to one place, the
documentation
about Apache 2 support.
1. It's not production ready
Ah yes - but that will contradict greatly, to the best version yet
marketing
trick the Apache Group is advertising on their front page.
We
I did more work and testing with fastcgi and apache 2, and have php 4.3
running under apache 2. Since it's out of process, no multithread
issues which are one of the major issues. I didn't write docs, but
there are some in sapi/cgi/README.fastcgi
Shane
As far as I can see, we should not
| We receive many complaints at [EMAIL PROTECTED] about failures in
| setting up PHP with Apache 2. Can somebody please update the
| documentation with details on Apache 2 on Linux and Windows, or
| provide information for the documentation team to add to the
| documentation. It would
| We receive many complaints at [EMAIL PROTECTED] about failures in
| setting up PHP with Apache 2. Can somebody please update the
| documentation with details on Apache 2 on Linux and Windows, or
| provide information for the documentation team to add to the
| documentation. It would
The aspect people complaining about is more a version thingie, e.g.
they try to set up php 4.2.3 with apache 2.0.43 and this could not
succeed. Is it really necessary to document that apache 2.03x works
only with php 4.2.x1, php4.2.x2 and apache 2.04x only with php4.2y1
or php4.2.y2? It
14 matches
Mail list logo