[J.T.]

Originally Posted by mistwang

If only used for that VHOST, just add it at vhost level.

OK thanks.

Originally Posted by mistwang

In command, use path to lsphp-5.3.2 binary.

Think I finally get it now. Please correct me if I'm wrong on the following findings.

Key fact: You can compile PHP only once per version.

Example, possible:

- PHP 5.2.13 with Mailparse, plus;
- PHP 5.3.2 with Curl, plus;
- PHP 5.3.1 with SOAP

Example, not possible:

- PHP 5.3.2 with Curl and Mailparse, plus;
- PHP 5.3.2 with SOAP and GD

LSWS references each instance of a PHP compilation by its version number, not by an arbitrarily set name. (Would be nice if this changed...)

Building on the example, possible, you can have one VH with external app pointing to $SERVER_ROOT/fcgi-bin/lsphp-5.3.2 and one to $SERVER_ROOT/fcgi-bin/lsphp-5.2.13 - simply edit the standard LSAPI App External App and update the Name, Socket Address and Command.

My use case works now. Thanks for your help.

If the above finding is correct, I'd make it a feature request to be able to "label" a certain PHP compile set with a unique arbitrarily chosen reference so withing fast-cgi folder, the PHP binary is referenced with this label. That way, we can have multiple binary compilations of the same PHP version with different PHP extensions. On a busy web server with many sites/scripts, this make environment isolation much easier and greatly helps with upgrade paths etc.