Netscape Server Application Programming Interface: Difference between revisions

Content deleted Content added
Rescuing 1 sources and tagging 0 as dead. #IABot (v1.6.2)
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5) (Whoop whoop pull up - 21816
 
(3 intermediate revisions by 3 users 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.
 
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://web.archive.org/web/20070328093147/http://httpd.apache.org/docs/1.3/misc/API.html |url-status=dead }}</ref>
 
==See also==
Line 38:
 
[[Category:Netscape]]
[[Category:World Wide Web]]
[[Category:Application programming interfaces]]