I have a question about the difrence of CGI or isapi

I must choose between CGI or ISAPI where I can run XOOPS on for the intranet site for 600 people.

I have heard that the speed of your website can decrease if you use Isapi.dll.

Is this true

ps what are the diffrence between the 2.

Thanks

Incorrect. ISAPI is actually a LOT faster under load as well as being more secure on a Windows IIS server. I would rate your options in this order;

CGI - Slow

ISAPI - Good to very good

FastCGI - Very fast!

In a nutshell (very simplistic overview here) CGI is an executable and is loading into and out of memory for every single request. ISAPI is a DLL and is loaded into memory once and then serves all requests from that one instance which makes it MUCH MUCH MUCH more efficient. FastCGI is also available as a DLL for Windows, but is more efficient than the default PHP ISAPI as it loads as one instance and then starts instances of php.exe as it needs them which saves on the memory loading/uunloading times which is the real killer for straight CGI.

I will be publishing an article at the end of next week (it's half finished now) regarding performance tuning XOOPS on IIS which will explain things for you more clearly. Keep an eye on my site (see sig) or the news items here on Xoops.org.

What is an example of a web server that supports FastCGI?
I've never tried it before.

It would be helpful to know what platform you planning to host on.

At http://cit.wvup.edu we're using FastCGI for our CentOS (Linux) web server using Apache.

I know it's not a good comparison since it's a PHP-Nuke :puke: site, but it should give you some idea.

Before anyone gives me any crap about the PHP-Puke site at the college, I didn't do it! Actually, we are planning on migrating to XOOPS over Christmas break. I've been holding out for 2.2.x Stable.

Hope this is helpful.

James

Quote:

Have a look here;

http://www.fastcgi.com/