Netscape Server Application Programming Interface: Difference between revisions

Revision as of 23:11, 1 April 2011

Revision as of 02:30, 13 August 2011

Line 21:

In contrast to CGI programs, NSAPI SAFs can be configured to run at different stages of request processing. For example, while processing a single [[HTTP]] request, different NSAPI SAFs can be used to authenticate and authorize the remote user, map the requested [[Uniform Resource Identifier|URI]] to a local file system path, generate the web page, and log the request.

After Netscape introduced NSAPI, [[Microsoft]] developed [[Internet Server Application Programming Interface|ISAPI]] and the [[Apache Software Foundation]] developed the [[Apache HTTP Server|Apache]] API. All three APIs have a number of similarities. LikeFor example: NSAPI, ISAPI and the Apache API allow applications to run inside the server process. Further, all three allow applications to participate in the different stages of request processing. For example, Apache API's hooks closely resemble those used in NSAPI.<ref>[http://httpd.apache.org/docs/1.3/misc/API.html Apache API notes<!-- Bot generated title -->]</ref>

==References==