From: Lindsay Haisley <fmouse-gentoo@fmp.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] PHP4
Date: Fri, 18 Jan 2008 11:29:53 -0600 [thread overview]
Message-ID: <1200677393.27864.58.camel@localhost.localdomain> (raw)
In-Reply-To: <20080118110850.C41241@shell.bway.net>
On Fri, 2008-01-18 at 11:10 -0500, A. Khattri wrote:
> So if we had waited we wouldn't have gone through the pain of
> upgrading servers to PHP5
The upgrade is reasonably painless. _Most_ code written for PHP4 will
run transparently on PHP5, assuming you have your php.ini files well
coordinated. Going forward, there are a number of very nice
enhancements in PHP5, notably a substantial improvement in OOP support.
You can also run both PHP4 and PHP5 at the same time and switch over on
a per-virtual server basis, so if you host lots of websites you don't
have to worry about possibly breaking all of them at once. The only
limitation here (which is an apache limitation, I think) is that either
v4 or v5 must run as CGI, which means that you can't use php_value
settings in a .htaccess file for the CGI version.
It's always a pleasure to work with well designed code.
--
Lindsay Haisley | "In an open world, | PGP public key
FMP Computer Services | who needs Windows | available at
512-259-1190 | or Gates" | http://pubkeys.fmp.com
http://www.fmp.com | |
--
gentoo-server@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-18 17:29 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 16:10 [gentoo-server] PHP4 A. Khattri
2008-01-18 16:12 ` Petteri Räty
2008-01-18 16:48 ` Jil Larner
2008-01-18 17:29 ` Lindsay Haisley [this message]
2008-01-22 16:13 ` Yves Thommes
2008-01-22 16:19 ` Andrew Gaffney
2008-01-22 18:12 ` Lindsay Haisley
2008-01-22 18:38 ` Yves Thommes
2008-01-22 18:53 ` Georges Toth
2008-01-22 18:55 ` Georges Toth
2008-01-22 19:13 ` Lindsay Haisley
2008-01-22 19:18 ` RijilV
2008-01-22 19:30 ` Lindsay Haisley
2008-01-22 19:42 ` Georges Toth
2008-01-22 20:22 ` Yves Thommes
2008-01-22 20:27 ` Andrew Gaffney
2008-01-22 20:37 ` Yves Thommes
2008-01-22 20:47 ` Qian Qiao
2008-01-22 21:12 ` Lindsay Haisley
2008-01-22 21:18 ` Andrew Gaffney
2008-01-22 23:02 ` Yves Thommes
2008-01-22 23:11 ` Qian Qiao
2008-01-22 23:15 ` RijilV
2008-01-22 23:41 ` Chashab
2008-01-23 8:37 ` Dumitru Moldovan
2008-01-23 0:39 ` Georges Toth
2008-01-22 21:42 ` pkoelle
2008-01-22 21:58 ` RijilV
2008-01-22 19:35 ` Georges Toth
2008-01-22 19:43 ` Greg Bowser
2008-01-22 19:46 ` Georges Toth
2008-01-22 19:48 ` Andrew Gaffney
2008-01-22 19:59 ` Greg Bowser
2008-01-22 19:54 ` Thilo Bangert
2008-01-22 19:56 ` Georges Toth
2008-01-22 19:10 ` Lindsay Haisley
2008-01-22 19:58 ` Thilo Bangert
2008-01-22 23:45 ` Yves Thommes
2008-01-23 0:00 ` Qian Qiao
2008-01-23 0:07 ` Lindsay Haisley
2008-01-22 18:16 ` Yves Thommes
2008-01-22 20:13 ` Petteri Räty
2008-01-22 20:31 ` Yves Thommes
2008-01-22 20:38 ` Qian Qiao
2008-01-22 20:46 ` Andrew Gaffney
2008-01-22 21:19 ` Lindsay Haisley
2008-01-22 21:20 ` Andrew Gaffney
2008-01-22 21:23 ` Lindsay Haisley
2008-01-22 21:35 ` Oliver Schad
2008-01-22 16:36 ` RijilV
2008-01-22 19:39 ` Matthias Bethke
2008-01-23 15:02 ` Matthew Summers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1200677393.27864.58.camel@localhost.localdomain \
--to=fmouse-gentoo@fmp.com \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox