Server application programming interface

Short description: API used to interface with web servers

In computing, server application programming interface (SAPI) is the direct module interface to web servers such as the Apache HTTP Server, Microsoft IIS, and Oracle iPlanet Web Server. In other words, SAPI is an application programming interface (API) provided by the web server to help other developers in extending the web server capabilities.

Microsoft uses the term Internet Server Application Programming Interface (ISAPI), and the defunct Netscape web server used the term Netscape Server Application Programming Interface (NSAPI) for the same purpose.[1]

As an example, PHP has a direct module interface called SAPI for different web servers;[2] in the case of PHP 5 and Apache 2.0 on Windows, it is provided in the form of a DLL file called php5apache2.dll,[3] which is a module that, among other functions, provides an interface between PHP and the web server, implemented in a form that the server understands. This form is what is known as a SAPI.

Different kinds of SAPIs exist for various web-server extensions. For example, in addition to those listed above, other SAPIs for the PHP language include the Common Gateway Interface (CGI) and command-line interface (CLI).[2][4]

## See also

* FastCGI (a variation of the CGI)

## References

1. ↑ "Netscape Server Application Programming Interface (NSAPI)". September 2005. http://searchsoa.techtarget.com/definition/Netscape-Server-Application-Programming-Interface. Retrieved 2013-09-22.
2. ↑ 2.0 2.1 "General Installation Considerations". http://php.net/manual/en/install.general.php. Retrieved 2013-09-22.
3. ↑ "PHP: Apache 2.x on Microsoft Windows". Archived from the original on 2013-09-26. https://web.archive.org/web/20130926122011/http://php.net/manual/en/install.windows.apache2.php. Retrieved 2013-09-22.
4. ↑ "Command line usage: Introduction". http://www.php.net/manual/en/features.commandline.introduction.php. Retrieved 2013-09-22.

## External links

* Developing modules for the Apache HTTP Server 2.4

* v
* t
* e

Web interfaces

Server-side|

| Protocols|

* HTTP
* CGI
* SCGI
* FCGI
* AJP
* WSRP
* WebSocket

|

Server APIs|

* C NSAPI
* C ASAPI
* C ISAPI
* COM ASP
* Java servlet
* container
* CLI OWIN
* ASP.NET Handler
* Python WSGI
* Ruby Rack
* JavaScript JSGI
* Perl PSGI
* Lua WSAPI
* Portlet
* container

Apache modules|

* mod include
* mod jk
* mod lisp
* mod mono
* mod parrot
* mod perl
* mod php
* mod proxy
* mod python
* mod wsgi
* mod ruby
* Phusion Passenger

Topics|

* Web resource vs. Web service
* Open API
* Webhook
* Application server
* comparison
* Scripting

Client-side|

| Browser APIs|

* C NPAPI
* LiveConnect
* XPConnect
* C NPRuntime
* C PPAPI
* NaCl
* ActiveX
* BHO
* XBAP

|

Web APIs|

| W3C|

* Audio
* Canvas
* CORS
* DOM
* DOM events
* EME
* File
* Geolocation
* IndexedDB
* MSE
* SSE
* SVG
* Video
* WebAuthn
* WebRTC
* WebSocket
* Web messaging
* Web storage
* Web worker
* XMLHttpRequest
* WebAssembly

|

Khronos|

* WebCL
* WebGL

Others|

* Gears
* Web SQL Database (formerly W3C)
* WebUSB

Topics|

* Ajax and Remote scripting vs. DHTML
* Mashup
* Web IDL
* Scripting

Topics|

* Dynamic web page
* Web standards
* Rich web application
* Web API security
* Web application
* Web framework

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Server application programming interface. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Server_application_programming_interface&oldid=3977802"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template