Netscape Server Application Programming Interface: Difference between revisions

Revision as of 20:10, 28 September 2024

Latest revision as of 21:55, 18 November 2024

(One intermediate revision by one other user not shown)

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.

<ref>After Netscape introduced NSAPI, [[Microsoft]] developed [[Internet Server Application Programming Interface|ISAPI]] and the [[Apache Software Foundation]] developed Apache API (or ASAPI: [[Apache HTTP Server|Apache Server]] API). All three APIs have a number of similarities. For example: NSAPI, ISAPI and 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 hooks closely resemble those used in NSAPI.<ref>{{cite web |title=Apache API notes |url=http://httpd.apache.org/docs/1.3/misc/API.html |access-date=2007-03-24 |archive-date=2007-03-28 |archive-url=https<ref><:/ref>/web.archive.org/web/20070328093147/http://httpd.apache.org/docs/1.3/misc/API.html |url-status=dead }}</ref>

</ref>

==See also==

*[[NPAPI]] (Netscape Plugin Application Programming Interface)

Line 34:

* [https://web.archive.org/web/20130713113125/http://support.zeus.com/zws/examples/2005/12/16/nsapi_netscape_server_api Zeus Web Server Introduction to NSAPI] (archived version)

{{Web interfaces}}<blockquote>

{{Netscape}}

[[Category:Netscape]]

[[Category:Application programming interfaces]]

</blockquote><noinclude></noinclude>