6 <META NAME="GENERATOR" CONTENT="Internet Assistant for Microsoft Word 2.0z">
\r
7 <STYLE TYPE="text/css">
\r
8 div.c5 {font-family: Arial Narrow; font-size: 80%; text-align: center}
\r
9 span.c4 {font-family: Courier}
\r
10 tt.c3 {font-family: Courier}
\r
11 div.c2 {text-align: center}
\r
12 div.c1 {color: #FFFFFF; font-family: Impact; font-size: 120%; text-align: center}
\r
15 <!--Copyright (c) 1996 Open Market, Inc. -->
\r
16 <!--See the file "LICENSE.TERMS" for information on usage and redistribution-->
\r
17 <!--of this file, and for a DISCLAIMER OF ALL WARRANTIES. -->
\r
18 <!-- $Id: fastcgi.htm,v 1.3 2001/11/27 01:13:29 robs Exp $ -->
\r
26 Technical White Paper<BR>
\r
30 A High-Performance Web Server Interface
\r
33 April 1996<!--Please send comments to:-->
\r
36 <!-- payne@openmarket.com-->
\r
41 The surge in the use of the Web by business has created a tremendous need for server extension applications
\r
42 that create dynamic content. These are the applications that will allow businesses to deliver products,
\r
43 services, and messages whose shape and content are in part determined by the interaction with, and knowledge
\r
44 of, the customers to which they are delivered.
\r
47 This important movement away from static Web content is pushing the limits and exposing the weaknesses of the
\r
48 environment in which these applications are currently bound: CGI (Common Gateway Interface). Most importantly
\r
49 it does not offer the performance these applications require. A new communication infrastructure is needed to
\r
50 connect Web servers with these new applications. This is what led Open Market to develop FastCGI.
\r
53 FastCGI is a fast, open, and secure Web server interface that solves the performance problems inherent in CGI,
\r
54 without introducing the overhead and complexity of proprietary APIs (Application Programming Interfaces).
\r
57 This paper assumes that the reader has basic familiarity with Web technology and developing Web applications.
\r
60 Common Gateway Interface
\r
63 The de facto standard interface for Web server applications is CGI, which was first implemented in the NCSA
\r
64 server. CGI has many benefits:
\r
68 <B>Simplicity.</B> <SPAN>It is easy to understand.</SPAN>
\r
71 <B>Language independence.</B> CGI applications can be written in nearly any language.
\r
74 <B>Process isolation.</B> Since applications run in separate processes, buggy applications cannot crash the
\r
75 Web server or access the server's private internal state.
\r
78 <B>Open standard.</B> Some form of CGI has been implemented on every Web server.
\r
81 <B>Architecture independence.</B> CGI is not tied to any particular server architecture (single threaded,
\r
82 multi-threaded, etc.).
\r
86 CGI also has some significant drawbacks. The leading problem is performance: Since a new process is created
\r
87 for each request and thrown away when the request is done, efficiency is poor.
\r
90 CGI also has limited functionality: It only supports a simple "responder" role, where the
\r
91 application generates the response that is returned to the client. CGI programs can't link into other
\r
92 stages of Web server request processing, such as authorization and logging.
\r
98 In response to the performance problems for CGI, several vendors have developed APIs for their servers. The
\r
99 two most notable are NSAPI from Netscape and ISAPI from Microsoft. The freely available Apache server also has
\r
103 Applications linked into the server API may be significantly faster than CGI programs. The CGI
\r
104 startup/initialization problem is improved, because the application runs in the server process and is
\r
105 persistent across requests. Web server APIs also offer more functionality than CGI: you can write extensions
\r
106 that perform access control, get access to the server's log file, and link in to other stages in the
\r
107 server's request processing.
\r
110 However, APIs sacrifice all of CGI's benefits. Vendor APIs have the following problems:
\r
114 <B>Complexity.</B> Vendor APIs introduce a steep learning curve, with increased implementation and
\r
118 <B>Language dependence.</B> Applications have to be written in a language supported by the vendor API
\r
119 (usually C/C++). Perl, the most popular language for CGI programs, can't be used with any existing
\r
123 <B>No process isolation.</B> <SPAN>Since the applications run in the server's address space, buggy
\r
124 applications can corrupt the core server (or each other). A malicious or buggy application can compromise
\r
125 server security, and bugs in the core server can corrupt applications.</SPAN>
\r
128 <B>Proprietary.</B> Coding your application to a particular API locks you into a particular vendor's
\r
132 <B>Tie-in to server architecture.</B> API applications have to share the same architecture as the server:
\r
133 If the Web server is multi-threaded, the application has to be thread-safe. If the Web server has
\r
134 single-threaded processes, multi-threaded applications don't gain any performance advantage. Also, when
\r
135 the vendor changes the server's architecture, the API will usually have to change, and applications
\r
136 will have to be adapted or rewritten.
\r
143 The FastCGI interface combines the best aspects of CGI and vendor APIs. Like CGI, FastCGI applications run in
\r
144 separate, isolated processes. FastCGI's advantages include:
\r
148 <B>Performance.</B> FastCGI processes are persistent-they are reused to handle multiple requests. This
\r
149 solves the CGI performance problem of creating new processes for each request.
\r
152 <B>Simplicity, with easy migration from CGI.</B> The FastCGI application library (described on page 9)
\r
153 simplifies the migration of existing CGI applications. Applications built with the application library can
\r
154 also run as CGI programs, for backward compatibility with old Web servers.
\r
157 <B>Language independence.</B> Like CGI, FastCGI applications can be written in any language, not just
\r
158 languages supported by the vendor API.
\r
161 <B>Process isolation.</B> A buggy FastCGI application cannot crash or corrupt the core server or other
\r
162 applications. A malicious FastCGI application cannot steal any secrets (such as session keys for
\r
163 encryption) from the Web server.
\r
166 <B>Non-proprietary.</B> FastCGI is supported in all of Open Market's server products, and support is
\r
167 under development for other Web servers, including the freely available Apache and NCSA servers, as well as
\r
168 commercial servers from Microsoft and Netscape.
\r
171 <B>Architecture independence.</B> The FastCGI interface is not tied to a particular server architecture.
\r
172 Any Web server can implement the FastCGI interface. Also, FastCGI does not impose any architecture on the
\r
173 application: applications can be single or multi-threaded, regardless of the threading architecture of the
\r
177 <B>Support for distributed computing.</B> FastCGI provides the ability to run applications remotely, which
\r
178 is useful for distributing load and managing external Web sites.
\r
182 The following sections describe the FastCGI interface, protocol, application library, and support in Open
\r
183 Market's WebServer products.
\r
186 2. FastCGI Interface
\r
189 The functionality provided by the FastCGI interface is very similar to that provided by CGI. To best
\r
190 understand the FastCGI protocol, we review the CGI interface here. Basic CGI request processing proceeds as
\r
195 For each request, the server creates a new process and the process initializes itself.
\r
198 The Web server passes the request information (such as remote host, username, HTTP headers, etc.) to the
\r
199 CGI program in environment variables.
\r
202 The Web server sends any client input (such as user-entered field values from an HTML form) to the CGI
\r
203 program's standard input.
\r
206 The CGI program writes any output to be returned to the client on standard output. Error information
\r
207 written to standard error is logged by the Web server.
\r
210 When the CGI process exits, the request is complete.
\r
214 FastCGI is conceptually very similar to CGI, with two major differences:
\r
218 FastCGI processes are persistent: after finishing a request, they wait for a new request instead of
\r
222 Instead of using operating system environment variables and pipes, the FastCGI protocol multiplexes the
\r
223 environment information, standard input, output and error over a single full-duplex connection. This allows
\r
224 FastCGI programs to run on remote machines, using TCP connections between the Web server and the FastCGI
\r
229 Request processing in a single-threaded FastCGI application proceeds as follows:
\r
233 The Web server creates FastCGI application processes to handle requests. The processes may be created at
\r
234 startup, or created on demand.
\r
237 The FastCGI program initializes itself, and waits for a new connection from the Web server.
\r
240 When a client request comes in, the Web server opens a connection to the FastCGI process. The server sends
\r
241 the CGI environment variable information and standard input over the connection.
\r
244 The FastCGI process sends the standard output and error information back to the server over the same
\r
248 When the FastCGI process closes the connection, the request is complete. The FastCGI process then waits for
\r
249 another connection from the Web server.
\r
253 FastCGI applications can run locally (on the same machine as the Web server) or remotely. For local
\r
254 applications, the server uses a full-duplex pipe to connect to the FastCGI application process. For remote
\r
255 applications, the server uses a TCP connection.
\r
258 FastCGI applications can be single-threaded or multi-threaded. For single threaded applications, the Web
\r
259 server maintains a pool of processes (if the application is running locally) to handle client requests. The
\r
260 size of the pool is user configurable. Multi-threaded FastCGI applications may accept multiple connections
\r
261 from the Web server and handle them simultaneously in a single process. (For example, Java's built-in
\r
262 multi-threading, garbage collection, synchronization primitives, and platform independence make it a natural
\r
263 implementation language for multi-threaded FastCGI applications.)
\r
269 FastCGI's ability to run applications remotely (over a TCP connection) provides some major benefits. These
\r
270 benefits are described in this section, along with some of the security issues that affect remote FastCGI
\r
274 FastCGI with Firewalls
\r
277 Applications that run on organizational (external) Web servers and depend on internal databases can be a
\r
278 challenge to administer. Figure 1 shows a typical organization, with an external Web server, a firewall
\r
279 restricting access to the internal network, and internal databases and applications.
\r
284 <IMG ALT="error-file:TidyOut.log" SRC="img00001.gif"><A NAME="_Ref352505891">Figure 1</A>
\r
287 With CGI and vendor APIs, the application has to run on the Web server machine. This means the server
\r
288 administrator has to replicate the necessary database information onto the system hosting the Web server
\r
289 (which may be difficult to do in an automated way without compromising firewall security). Or, the
\r
290 administrator may build a "bridge" that allows access through the Web server to internal databases
\r
291 and applications (which is effectively re-inventing remote FastCGI).
\r
294 With remote FastCGI, the applications can run on the internal network, simplifying the administrator's
\r
295 job. When used with appropriate firewall configuration and auditing, this approach provides a secure,
\r
296 high-performance, scalable way to bring internal applications and data to the external network.
\r
302 For resource-intensive CGI and API applications, the Web server machine quickly becomes the bottleneck for
\r
303 overall throughput. The usual way to solve this performance problem is to buy a bigger, faster Web server
\r
304 machine, or to partition the Web site across several Web servers.
\r
307 With remote FastCGI, the resource-intensive applications can be moved off the Web server machine, giving the
\r
308 server administrator additional flexibility in configuring the Web server. The administrator can configure
\r
309 FastCGI applications "behind the scenes" without having to change any content links or the external
\r
310 view of the Web site. The administrator can use several smaller, inexpensive server machines for applications,
\r
311 and can tailor each machine to the application it is hosting.
\r
314 Security Issues with Remote FastCGI
\r
317 The two security issues with remote FastCGI connections are authentication and privacy. FastCGI applications
\r
318 should only accept connections from Web servers that they trust (the application library includes support for
\r
319 IP address validation). Future versions of the protocol will include support for applications authenticating
\r
320 Web servers, as well as support for running remote connections over secure transport protocols such as SSL or
\r
321 PCT.<!--This pargraph needs to be made stronger, going into the issues in a little more detail.-->
\r
324 The FastCGI Protocol
\r
327 This section offers a brief introduction to the protocol used on the connection between the Web server and
\r
328 FastCGI application. Most application developers will use the FastCGI application library and won't have
\r
329 to worry about the protocol details. However, specialized applications are free to implement the FastCGI
\r
333 FastCGI uses a simple packet record format on the connection between the application and the Web server. The
\r
334 same record format is used in both directions and is outlined in Figure 2.
\r
339 <IMG ALT="error-file:TidyOut.log" SRC="img00002.gif"><A NAME="_Ref352404075">Figure 2</A>
\r
342 The protocol version field specifies the version of the FastCGI protocol that is in use. The type field
\r
343 specifies the type of the record (described in the following section). The request ID identifies this record
\r
344 to a particular request, allowing multiple requests to be multiplexed over a single connection. The data
\r
345 length field specifies the number of data bytes that follow.
\r
348 The different FastCGI packet types are:
\r
353 <TT CLASS="c3">FCGI_PARAMS</TT>
\r
356 Used for sending name/value pairs (CGI environment variables) from the Web server to the application.
\r
361 <TT CLASS="c3">FCGI_STDIN</TT>
\r
364 Used for sending the standard input from the Web server to the application.
\r
369 <TT CLASS="c3">FCGI_DATA</TT>
\r
372 Used for sending filter data to the application (for more information, see the filter role described on
\r
378 <TT CLASS="c3">FCGI_STDOUT</TT>
\r
381 Used to send standard output from the application to the Web server.
\r
386 <TT CLASS="c3">FCGI_STDERR</TT>
\r
389 Used to send standard error information from the application to the Web server.
\r
394 <TT CLASS="c3">FCGI_END_REQUEST</TT>
\r
397 Ends the request (can be sent by either the server or the application).
\r
404 For complete protocol details, see the <I>FastCGI Protocol Specification</I>, available from the Web site
\r
405 listed at the end of this paper.
\r
408 3. Application Roles
\r
411 A major problem with CGI is its limited functionality: CGI programs can only provide simple responses to
\r
412 requests. FastCGI provides expanded functionality with support for three different application
\r
417 <B>Responder.</B> This is the basic FastCGI role, and corresponds to the simple functionality offered by
\r
421 <B>Filter.</B> The FastCGI application filters the requested Web server file before sending it to the
\r
425 <B>Authorizer.</B> The FastCGI program performs an access control decision for the request (such as
\r
426 performing a username/password database lookup).
\r
430 Other roles will be defined in the future. For instance, a "logger" role would be useful, where the
\r
431 FastCGI program would receive the server's log entries for real-time processing and analysis.
\r
434 The roles are described in more detail in the following sections.
\r
440 FastCGI's Responder role is identical to the functionality provided by CGI today. When a request comes
\r
441 into the server, the FastCGI program generates the response that's returned to the client (typically an
\r
445 <A NAME="_Ref352404524">Filter Role</A>
\r
448 The Filter role allows a FastCGI application to process a requested file before it is returned to the client.
\r
451 Let's assume that the Web server is configured so that all files with the .<TT CLASS="c3">sgml</TT>
\r
452 extension are processed by a SGML-to-HTML FastCGI filter application, and the user accesses the following URL:
\r
455 <TT CLASS="c3">/document.sgml</TT>
\r
458 After the Web server makes an access control decision and maps this URL to a content file, it invokes the
\r
459 FastCGI filter application with this file available as input. The FastCGI program's HTML output is sent
\r
460 back to the client, just as in the responder role. The process is outlined in Figure 3.
\r
465 <IMG ALT="error-file:TidyOut.log" SRC="img00003.gif"><A NAME="_Ref352560526">Figure 3</A>
\r
468 Filter applications can significantly improve performance by caching filter results (the server provides the
\r
469 modification time in the request information so that applications can flush the cache when the server file has
\r
473 The Filter role is useful for:
\r
477 On-the-fly format conversions
\r
480 Dynamic documents (such as documents with embedded SQL queries, or dynamic advertisement insertion)
\r
483 Applying a standard template: headers, footers, and backgrounds
\r
490 The Authorizer role allows a FastCGI application to make an access control decision for a request. The FastCGI
\r
491 application is invoked with all of the request information, just as in the Responder role. If the authorizer
\r
492 application generates a "200 OK" HTTP result, the Web server assumes that access is allowed and
\r
493 proceeds with the request. (The Web server may process other access checks, including other FastCGI
\r
494 authorizers, before access is ultimately allowed.) If the application generates any other response, that
\r
495 response is returned to the client and the request is ended. The response can be any valid HTTP response,
\r
496 including "Access Denied" or "Redirect".
\r
499 The Authorizer role is useful for:
\r
503 Access control based on username and password, where the user information is looked up in an external
\r
507 Complex access policies, such as time-of-day based access.
\r
510 Smart-card challenge/response authentication.
\r
513 Dynamic redirects, where the user is sent to different pages based on the request profile.
\r
517 <A NAME="_Ref352251764">4. FastCGI Application Library</A>
\r
520 Open Market has developed a FastCGI application library that implements the FastCGI protocol (hiding the
\r
521 protocol details from the developer). This library makes implementing FastCGI programs as easy as writing CGI
\r
525 The application library provides a replacement for the C language standard I/O (stdio) routines, such as <TT
\r
526 CLASS="c3">printf()</TT> and <TT CLASS="c3">gets()</TT>. The library converts references to standard input,
\r
527 standard output, and standard error to the FastCGI protocol. References to other files "fall
\r
528 through" to the underlying operating system standard I/O routines.
\r
531 This approach has several benefits:
\r
535 Developers don't have to learn a new API to develop FastCGI applications.
\r
538 Existing CGI programs can be migrated with minimal source changes (CGI migration is described in more
\r
539 detail in the following section).
\r
542 FastCGI interpreters for Perl, Tcl, and other interpreted languages can be built without modifying the
\r
543 interpreter source code.
\r
547 Here's a simple FastCGI application:
\r
552 #include <fcgi_stdio.h>
\r
557 while(FCGI_Accept() >= 0) {
\r
558 printf("Content-type: text/html\r\n");
\r
559 printf("\r\n");
\r
560 printf("Hello world!<br>\r\n");
\r
561 printf("Request number %d.", count++);
\r
567 This application returns a "Hello world" HTML response to the client. It also keeps a counter of the
\r
568 number of times it has been accessed, displaying the value of the counter at each request.
\r
571 The <TT>fcgi_stdio.h</TT> header file provides the FastCGI replacement routines for the C standard I/O
\r
572 library. The <TT>FCGI_Accept()</TT> routine accepts a new request from the Web server.
\r
575 Migrating Existing CGI Programs
\r
578 The application library was designed to make migration of existing CGI programs as simple as possible. Many
\r
579 applications can be converted by adding a loop around the main request processing code and recompiling with
\r
580 the FastCGI application library. FastCGI applications have the following structure, with an initialization
\r
581 section and a request processing loop:
\r
584 <I>Initialize application;<BR>
\r
585 </I> <TT>while(FCGI_Accept() >= 0) {</TT><BR>
\r
586 <I>Process request</I>;<BR>
\r
590 To ease migration to FastCGI, executables built with the application library can run as either CGI or FastCGI
\r
591 programs, depending on how they are invoked. The library detects the execution environment and automatically
\r
592 selects FastCGI or regular I/O routines, as appropriate.
\r
595 After migration, developers can clean up their FastCGI applications for best performance:
\r
599 Fix any resource leaks. Many CGI programs do not attempt to manage memory or close files, because they
\r
600 assume the world is going to be cleaned up when they exit. (If you don't want to clean up your program,
\r
601 you can just have your process assume that it is leaking memory and exit after processing some fixed number
\r
602 of requests.) Purify from Pure Software is one of a number of excellent tools for finding leaks and other
\r
603 memory use problems.
\r
606 Fix any problems with retained application state. The application must ensure that any state that it
\r
607 creates in processing one request has no unintended effects on later requests.
\r
610 Collapse functionality. A common practice with CGI applications is to implement many small programs, with
\r
611 one function per program. CGI encourages this, because smaller programs load faster. With FastCGI, it's
\r
612 better to have related functionality in a single executable, so there are fewer processes to manage and
\r
613 applications can take advantage of sharing cached information across functions.
\r
617 Applications written in Perl, Tcl, and other scripting languages can be migrated by using a language
\r
618 interpreter built with the application library. FastCGI-integrated Tcl and Perl interpreters for popular Unix
\r
619 platforms are available from Open Market. The interpreters are backward-compatible: They can run standard Tcl
\r
620 and Perl applications.
\r
623 5. FastCGI in the Open Market WebServer
\r
626 This section describes the FastCGI support in the following Open Market server products:
\r
630 Open Market WebServer V2.0
\r
633 Open Market Secure WebServer V2.0
\r
636 Open Market Secure WebServer (Global) V2.0
\r
640 For more information about FastCGI support, see the <I>Open Market WebServer Installation and Configuration
\r
644 Server Configuration
\r
647 FastCGI applications are configured with the server's configuration file. Configuration has two parts.
\r
650 First, the server administrator defines an <I>application class</I>. For local applications, the application
\r
651 class specifies the details of running the FastCGI application, such as:
\r
655 The pathname of the application executable.
\r
658 Any arguments and environment variables to pass to the process at startup.
\r
661 The number of processes to run.
\r
665 For remote applications, the class configuration information includes the host and TCP port to connect to. The
\r
666 Web server assumes that the FastCGI application has been started on the remote host. If a request comes in and
\r
667 the server can't connect to the FastCGI TCP port, the server logs an error and returns an error page to
\r
671 The second configuration step is mapping the application class to a role:
\r
675 For responder roles, the administrator configures some part of the URL space to be handled by the FastCGI
\r
676 application. For example, all URLs beginning with <SPAN CLASS="c4">/rollcall/</SPAN> might be handled by
\r
677 the employee database application.
\r
680 For filter roles, the administrator configures a file extension to be handled by a filter application. For
\r
681 example, all files with the <SPAN CLASS="c4">.sql</SPAN> extension could be handled by a SQL query lookup
\r
685 For authorizer roles, the administrator configures an authorizer application in the same manner as other
\r
686 access methods (hostname, username/password, etc.) A request must pass <I>all</I> access control checks
\r
687 (possibly including multiple FastCGI authorizers) before access is allowed.
\r
694 To simplify migration for existing CGI programs, the WebServer provides a simple way to install new FastCGI
\r
695 programs without having to reconfigure the server. However, this approach doesn't offer all of the
\r
696 performance benefits of FastCGI application classes.
\r
699 The WebServer treats any file with the extension <SPAN CLASS="c4">.fcg</SPAN> as a FastCGI application. When a
\r
700 request corresponds to such a file, the WebServer creates a new FastCGI process to handle the request, and
\r
701 shuts down the process when the request is complete (just as in CGI). In this mode of operation performance is
\r
702 comparable to CGI. Future versions of the WebServer will improve performance by automatically caching
\r
703 processes and re-using them for subsequent requests.
\r
709 FastCGI programs can improve performance by caching information in the application process. For applications
\r
710 that require frequent but expensive operations such as validating a username/password in an external database
\r
711 for each request, this technique can significantly improve performance.
\r
714 To improve the effectiveness of this technique, the WebServer implements <I>session affinity</I>. When session
\r
715 affinity is enabled, the WebServer arranges for all requests in a user session to be handled by the same
\r
716 FastCGI application process. What constitutes a "session" is configurable. The default configuration
\r
717 uses the WebServer's built-in session tracking facility to identify user sessions. However, the server
\r
718 administrator can use any part of the request information for the session affinity mapping: the URL path, the
\r
719 client's hostname, the username, etc.
\r
720 <!--Talk about applications that need to hold onto resources for the user (such as open connections to the database).-->
\r
723 6. FastCGI Performance Analysis
\r
726 How fast is FastCGI? The answer depends on the application. This section contains some real FastCGI
\r
727 performance measurements, as well as guidelines for estimating the FastCGI speedup.
\r
733 We measured the relative performance of CGI, FastCGI, and static files on the Open Market WebServer, using a
\r
734 simple application that generates a fixed number of output bytes. The following table shows the measured
\r
735 request processing time for different request types on a typical platform. The times are measured from the
\r
736 client perspective and include client, server, and application processing time.
\r
738 <TABLE BORDERCOLOR="#000000" BORDER="2">
\r
747 21ms + 0.19ms per Kbyte
\r
759 22ms + 0.28ms per Kbyte
\r
771 59ms + 0.37ms per Kbyte
\r
777 FastCGI performance is comparable to serving static files, and significantly better than CGI (clearly showing
\r
778 the high overhead for process creation). Real applications have an additional time component: process
\r
779 initialization, which should be added to overall request processing time.
\r
782 Let's use this data to estimate the speedup from migrating a typical database CGI application to FastCGI.
\r
783 Assume the application takes 50ms to initialize the database connection and generates 5K of output data.
\r
784 Request performance can be computed as follows:
\r
792 59ms + 50ms + (0.37ms)(5) = 111ms
\r
800 22ms + (0.28ms)(5) = 23ms
\r
805 In this example, FastCGI has a 5x performance advantage over CGI, mostly due to savings from not having to
\r
806 create and initialize new processes for each request.<!--Need to talk about FastCGI vs proprietary APIs.-->
\r
812 Today's Web business applications need a platform that's fast, open, maintainable, straightforward,
\r
813 stable, and secure. FastCGI's design meets these requirements, and provides for a logical extension from
\r
814 proven and widely deployed CGI technology. This allows developers to take advantage of FastCGI's benefits
\r
815 without losing their existing investment in CGI applications.<!--Need to talk about NT.-->
\r
817 <!--Need to give "more punch" to this conclusion: include info about uses for FastCGI (accessing legacy data in databases, access control, distributed applications, apps that have to run in multiple OS environments. -->
\r
820 8. For More Information
\r
823 For more information about Open Market and our products, visit our Web site at:<SPAN CLASS=
\r
824 "c4">http://www.openmarket.com/</SPAN>
\r
827 For more information about the FastCGI protocol and the developer's kit, and the latest information about
\r
828 FastCGI standardization and support in other Web servers, visit the FastCGI project page at:<SPAN CLASS=
\r
829 "c4">http://www.openmarket.com/fastcgi/</SPAN>
\r
projects / catagits/fcgi2.git / blob