Talk:Internet Server Application Programming Interface

Revert dated 4th Dec 06

I reverted the previous update because, although not vandalism, it was poorly worded and removed many of the tags already added to the page. I think maybe some of the ideas are valid; perhaps someone with more knowledge than I can incorporate them:

"It consists of a set of program calls that can be used to include while writing a Web Server application. The advantage of ISAPI is that the applications run faster than the counterpart CGI-based applications. It is possibe to create a dynamic link library application file using ISAPI that can support the process and address space of the HTTP application. Since ISAPI supports COM/DCOM technology, it naturally provides a vendor independent way of providing many features of the web server."

Stu 01:18, 4 December 2006 (UTC)

Picture

All articles in Wikipedia are supposed to have an illustration - some kind of graphic. I've gone ahead and added one, but I don't know how to shrink it down and still have the full one available using the media wiki software. Maybe I need to upload two different files, I dunno?

Also I added a section called "The Big Picture" that explains not only what ISAPI is, but how it fits into the picture and why it's needed. My hope is that this will help readers gain the better understanding they came to the encyclopedia for. —The preceding unsigned comment was added by DigitalEnthusiast (talk • contribs) 23:02, 4 December 2006 (UTC).

I set the image to display as a thumbnail, and added the caption. I think it should stay smaller than full-size, but any other beneficial changes are welcome. RobLinwood 01:20, 9 December 2006 (UTC)

ISAPI components can be developed in...

This page contradicts itself:

• "Both Filters and Extensions must be written in C++ and compiled into DLL files which are then registered with IIS to be run on the web server."
• "ISAPI applications can be developed using any development tool that can generate a Win32 DLL."

The latter sounds much more likely than the former to me, because, if ISAPI DLLs really had to be written in C++, it would open up a mass of binary compatibility issues that would make development all but impossible on anything but Microsoft Visual C++. The writer of the former is likely confused by the fact that native support for ISAPI is only available for C++ (and apparently Delphi as well, as mentioned in the rest of the article) which makes it more difficult to write ISAPI extensions in other languages, but certainly far from impossible. 212.178.108.2 15:19, 15 November 2007 (UTC)

Still contradictory

"Both Filters and Extensions must be written in C++ or C# and compiled into DLL files ..." Then the next sentence is "ISAPI applications can be written using C++, C#, and Delphi Pascal." —Preceding unsigned comment added by 128.197.24.76 (talk) 20:05, 2 May 2008 (UTC)

Performance

There is a section including heading of "performance", but no mention is made of performance, only downsides. Compared to scripts, unmanaged compiled binary including a dll should be *many* times faster, (often over 100 times faster). Even compared to a fancy script compiler (JIT binary compiler which currently is rare) the binary may be several times faster, as the safety of managed code adds overhead. (Protecting against buffer overruns, etc and perhaps having seperate process adds overhead, as price of making bugs less dangerous.) —Preceding unsigned comment added by 142.59.198.91 (talk) 14:49, 20 April 2009 (UTC)