NSAPI (Netscape Server Application Programming Interface) is an (application program interface) that is provided with Netscape Web server to help developers build faster and more complex Web-based applications by extending the server capabilities. NSAPI, the Common Gateway Interface (CGI), and the Java and JavaScript-based server API are the three components of Netscape's Internet Application Framework. NSAPI is more than CGI efficient and safe.
Through the built-in server applications, NSAPI Netscape Enterprise Services to handle the HTTP request response exchange process. Netscape Server Application Server (SAF) prepared using the NSAPI server call these functions to handle the request sent by the client. Initialized at the beginning of the server from the client to wait for HTTP requests for resources, such as HTML documents, CGI programs, or image files. Uniform Resource Identifier of the request is made by and the client and the HTTP method of composition information. Request response process includes the following six steps:
1. AuthTrans, which verifies request information (name and password, for example);
2. NameTrans, which translates the in the request into a local file system path;
3. PathCheck, which checks the validity of the path and the authorization of the user for path access;
4. ObjectType, which determines the MMIE (Multi-purpose Internet Mail Encoding) type of the resource requested by the client;
5. Service, which is the response to the client; and finally,
6. AddLog, which adds related entries to the log file.
Each step contains multiple operations, the Server Application Function (SAF) implementation. Each SAF is a result code back to the server restored to illustrate the operation is not successful. Based on this result code, the server will choose to further steps, to the current step to the next SAF or terminate the program.
Do you think NSAPI is helpful??
Internet references
Netscape Server Application Programming Interface (SAPI), Retrieved on 15 March 2011
URL:http://searchsoa.techtarget.com/definition/Netscape-Server-Application-Programming-Interface
Through the built-in server applications, NSAPI Netscape Enterprise Services to handle the HTTP request response exchange process. Netscape Server Application Server (SAF) prepared using the NSAPI server call these functions to handle the request sent by the client. Initialized at the beginning of the server from the client to wait for HTTP requests for resources, such as HTML documents, CGI programs, or image files. Uniform Resource Identifier of the request is made by and the client and the HTTP method of composition information. Request response process includes the following six steps:
1. AuthTrans, which verifies request information (name and password, for example);
2. NameTrans, which translates the in the request into a local file system path;
3. PathCheck, which checks the validity of the path and the authorization of the user for path access;
4. ObjectType, which determines the MMIE (Multi-purpose Internet Mail Encoding) type of the resource requested by the client;
5. Service, which is the response to the client; and finally,
6. AddLog, which adds related entries to the log file.
Each step contains multiple operations, the Server Application Function (SAF) implementation. Each SAF is a result code back to the server restored to illustrate the operation is not successful. Based on this result code, the server will choose to further steps, to the current step to the next SAF or terminate the program.
Do you think NSAPI is helpful??
Internet references
Netscape Server Application Programming Interface (SAPI), Retrieved on 15 March 2011
URL:http://searchsoa.techtarget.com/definition/Netscape-Server-Application-Programming-Interface
