|
Search tenon.com
Thanks to:
|
|
iTools
on 8/22/00 3:47 PM, Robin Böckman at robin@xxxxxxxxx wrote:
> itools@xxxxxxxxxxxxxxx writes:
>> The "final" release of the PHP4 module did have a lot
>> of the modules
>> compiled as dynamically loadable. Check the current
>> PHP4 download
>> and see what you think.
>
>
> could you give us a quick pointer how to slim down the
> modules, and is their something to gain by this?
Oh crud...I've started something now...
It has to be done at compile time for PHP4. The advantage is the same as
with dynamic modules for Apache. If you don't need a certain module or
capability, you can disable it. In a dynamic loading environment, the
software doesn't take up as much of a footprint in memory due to the fact
that it only loads what is required.
There's also the possibility of reducing the number of possible
bugs/glitches.
Example: If you're never ever going to use WebObjects, why would you want to
keep that module loaded in Apache? If you're never ever going to use
TrueType features in PHP4, then why would you want to keep that module
loaded? If you decided to use either, it would be simple matter of
reactivating them again in a configuration file instead of having to
recompile anything.
Todd Daniel Woodward
Technical Consultant
RadioDigest.com
http://radiodigest.com
----
Tenon Intersystems' iTools Mailing List
To unsubscribe: send mail to itools-request@xxxxxxxxx
with the subject: unsubscribe
|
| Tenon Home |
Products |
Order |
Contact Us |
About Tenon |
Register |
Tech Support |
Resources |
Press Room |
Mailing Lists |
|
Copyright©2003 Tenon Intersystems, 232 Anacapa Street, Suite 2A, Santa Barbara,
CA 93101. All rights reserved.
Questions about our website - Contact:
webmaster@tenon.com.
|
|