Re: [PHP4BETA] What is ext/lcg/lcg.c?
| From: | Zeev Suraski | Date: | Mon, 30 Aug 1999 20:07:37 +0000 |
| Subject: | Re: [PHP4BETA] What is ext/lcg/lcg.c? | ||
| References: | 1 2 3 4 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-3882@lists.php.net to get a copy of this message | ||
At 08:54 30/08/99 , Sascha Schumann wrote:
We can take A2 into account now, but it would make much more sense to wait until even the Apache developers get a brighter clue as to what it's going to be like exactly. They're brainstorming a lot, and recently they (Dean) actually started writing some code that might actually be the framework for Apache 2.0's core, but I doubt it's anywhere near its final form. We don't know what kind of hooks Apache 2.x is going to have, mainly because neither do the Apache developers."We should take Apache 2 into account."That does not mean that we should _depend_ on A2 which is implied by you. It refers to the design process - if we avoid steps which make it hard to interact with A2, then we "take A2 into account."And, put the discussion about whether A2 is around the corner or not by side, at some point in time we will have to deal with it. My intention is therefore focused on avoiding mistakes, rather than planting A2 specific hooks into SAPI.
The session module isn't platform specific nor does it
contain platform specific code. It just happens to be faster
for sites which use shared memory to store the session data.
Once you port mm to platform X, the session module will be
able to use shared memory there.
MM is currently UNIX specific (as far as I recall, it's shared memory based). You might be able to emulate its behavior under Win32 or a multithreaded environment, you might not. Either way, until you do, it's platform specific (whether you use a platform specific function or a platform specific library that may or may not be ported later on doesn't make much of a difference; Everything can be ported or emulated, it doesn't mean its done).
My rule of the thumb here is simple - if something works under most unices and Win32, it's platform independent. If it doesn't, it's not. Therefore, your session code that relies on the UNIX specific MM library is platform dependent, as it would not work under Win32 (and perhaps not on multithreaded UNIX platforms, not sure about that though). It doesn't mean you shouldn't use it in your session module - but it does mean it shouldn't be encouraged and introduced as a part of PHP's infrastructure for module development.
Zeev
--
Zeev Suraski <zeev@zend.com> http://www.zend.com/
For a PGP public key, finger bourbon@netvision.net.il