c/c++ shared modules as plugins

[mistwang]

Yes, parsed SSI code are cached in memory.

[Marcus]

Is SSI going to be available in the standard version of LSWS or just the Enterprise version?

Can you list which SSI features are currently available please (e.g. include virtual="...", set var="...")? Thanks.

Also, what variables are automatically available in SSI - i.e. ones that can be used in <!--# echo ...> declarations? (e.g. request_uri, server_ip...).

[mistwang]

SSI is available in standard edition. Cache is Enterprise 2-CPU and above.
Our SSI implementation should be up to the spec of Apache mod_ssi.

[Marcus]

How does one enable SSI?

[mistwang]

assign MIME "application/x-httpd-shtml" to the corresponding file suffix.

[Marcus]

We may implement something like ISAPI or NSAPI as the internal API. Only need one, will investigate which one is better.
Right now, we have LSAPI similar to FastCGI as external application API. We can even implement something like LSAPI-ISAPI bridge to load ISAPI app into a external process, so the server reliability wont be affect by the third party application, once the application is stable, can load it to the web server internal for maximum performance.

Any idea of timeframe for implementing an ISAPI or LSAPI-ISAPI bridge? I think it could be a really useful feature, especially for the larger websites.

[mistwang]

It is a low priority feature at this moment, we need to work on the 4.0 feature list first.

[Marcus]

Sure, I understand. Good luck with getting the 4.0 featureset done.