php-windows Digest 6 Jun 2004 21:32:14 -0000 Issue 2275
Topics (messages 23921 through 23924):
Re: IIS5, ISAPI PHP Slow load after timeout
23921 by: Alan McDonald
23922 by: Svensson, B.A.T. (HKG)
Feature request for PHP on windows
23923 by: Shrock, Court
23924 by: \[php\]Walter
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
--- Begin Message ---
Is there any way to build the isapi version of PHP such that there is no
small stub dll (i.e. php4isapi.dll) and the main dll php4ts.dll - but
instead to have one monolithic dll. This would force IIS to load and cache
the dll permanently.
Alan
"Alan McDonald" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I have Win2000 Server, PHP4 installed with ISAPI module.
> Output_buffer is ON
> php4isapi is in the c:\php directory
> php4ts.dll is in the system32 directory.
> All works OK especially when traffic is high to the site.
> But when traffic is low and I assume a timeout expires, it appears to me
> that php4ts.dll is unloaded and only reloads when another page is hit.
Then
> it remains until I leave the site inactive for a period. Then after
hitting
> the site a few times, pages are delivered quite fast again.
> Is there a way of forcing php4ts.dll to remain loaded? if this is in fact
> the problem. I know php4isapi.dll remains loaded because I can't rename it
> while the application is loaded but I can rename php4ts.dll after a period
> of idle activity, so it doesn't remain loaded.
> Anyone try adding it to the application list?
> Alan
--- End Message ---
--- Begin Message ---
Wouldn't a static DLL solve this?
-----Original Message-----
From: Alan McDonald
To: [EMAIL PROTECTED]
Sent: 4-6-2004 15:59
Subject: [PHP-WIN] Re: IIS5, ISAPI PHP Slow load after timeout
Is there any way to build the isapi version of PHP such that there is no
small stub dll (i.e. php4isapi.dll) and the main dll php4ts.dll - but
instead to have one monolithic dll. This would force IIS to load and
cache
the dll permanently.
Alan
"Alan McDonald" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I have Win2000 Server, PHP4 installed with ISAPI module.
> Output_buffer is ON
> php4isapi is in the c:\php directory
> php4ts.dll is in the system32 directory.
> All works OK especially when traffic is high to the site.
> But when traffic is low and I assume a timeout expires, it appears to
me
> that php4ts.dll is unloaded and only reloads when another page is hit.
Then
> it remains until I leave the site inactive for a period. Then after
hitting
> the site a few times, pages are delivered quite fast again.
> Is there a way of forcing php4ts.dll to remain loaded? if this is in
fact
> the problem. I know php4isapi.dll remains loaded because I can't
rename it
> while the application is loaded but I can rename php4ts.dll after a
period
> of idle activity, so it doesn't remain loaded.
> Anyone try adding it to the application list?
> Alan
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--- End Message ---
--- Begin Message ---
How about using the registry to store the location of the php.ini. It could
default to c:\windows for backward compatibility. I currently have multiple
versions of PHP setup on the same system. This works fine, as long as I
don't use the ISAPI module because the path to php.ini is hardcoded to
c:\windows with the dll. I'd like to test ISAPI configurations before
"going live" but still have the ability to easily maintain/update to newer
versions of PHP.
The folks at Zend have done exactly that in their bundled version of PHP.
--- End Message ---
--- Begin Message ---
"Court Shrock" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> How about using the registry to store the location of the php.ini. It
could
> default to c:\windows for backward compatibility. I currently have
multiple
> versions of PHP setup on the same system. This works fine, as long as I
> don't use the ISAPI module because the path to php.ini is hardcoded to
> c:\windows with the dll. I'd like to test ISAPI configurations before
> "going live" but still have the ability to easily maintain/update to newer
> versions of PHP.
>
> The folks at Zend have done exactly that in their bundled version of PHP.
NO, NO, please NO!
No registry!
God please, No!
I have a complete Apache, Perl, mySQL and PHP install on my NT (works 2k and
XP BTW) and I have NO registry settings! None! I don't want them!
I back up my G volume to CD, and when my windows box dies (which it does all
too often) all I have to do is restore from the CD, add some env vars and
I'm in business!
Now, if Windows PHP would be made "smart" enough to look in it's current dir
FIRST for its INI, then I, and others, can run multiple versions of PHP
without a problem.
Why this was not done in the first place I have no idea. I just figured the
guys who made it had a real good, windows limiting, reason for doing what
they did. (I hope)
So please, I vote -1 on a registry setting.
BTW: add the env var PHPRC with the path to your PHP install and PHP will
look there for the INI. But again, this only works for a single PHP install.
Walter
--- End Message ---
