JavaServer Pages

pdf.css

You are here: CodeIdol > Java > JavaServer Pages > page: 14 15 16 17 18 19 20 21 22 23 24

the new one started, and the Web server needs to close down the socket and open a new
one. Installing a brand new Fast CGI is even more difficult and will typically require
some change to the Web server's configuration describing where the Fast CGI process is
running and other information. Most Fast CGI implementations will make this process as
automated as possible, but it may still require special system privileges to make all the
changes happen.
Fast CGIs can be written in C, Perl, or numerous other languages. Typically, the
programs look like regular CGIs, with perhaps some additional code at the beginning.
This makes it very easy for programmers to learn how to write Fast CGIs, but it leaves all
the same problems regarding the intermingling of program code and HTML.
Since the development of Fast CGIs, a few modifications to address these problems have
been made. Most of the popular Web servers can address the problem of too many
separate processes by allowing new dynamic functionality to be added to the Web server
itself. The idea is that new capabilities can be added to the Web server; when it sees a
request that it formerly would have passed off to a CGI, the Web server instead invokes
the new routines. This greatly enhances the speed of requests, as everything now stays in
one process. This architecture is illustrated in
Figure 1.4
.
Figure 1.4. Web server extensions.
You are here: CodeIdol > Java > JavaServer Pages > page: 14 15 16 17 18 19 20 21 22 23 24

Related tags

Popular Categories

Unix books and guides

AJAX popular information
C# language guides
Windows books and cookbooks
.......

Русский

Polski

Francais

Deutsch

support

sitemap

terms