Installation guide

Interactive Multiuser Web Applications
FlashCONNECT Administrator’s Guide 21
This example continues using the URL in the diagram above. When a URL is entered
into the browser the following occurs:
• Address portion of the URL (http://www.hostname.com/) is used to contact the
Web server at that address and requests the specified page (/cgi-bin/
fccgi.exe?).
• Web server processes the request and, since the requested page is an
application, executes the application.
• Web server starts fccgi.exe, fcisapi.dll, or FCServlet which read and parse the
remaining information from the URL (w3exec=application) and any submitted
Web form. fccgi.exe, fcisapi.dll, or FCServlet then connect to FCService,
passing in the environment variables, including the value of w3exec.
• FCService sees that a value for w3exec is specified, so it selects an unused
connection to the database server and passes the information from the URL and
Web form to WWW-IRUN.
• FCService sends the information to WWW-IRUN and starts the application
specified by the value of w3exec.
The process to return information to the browser is:
• Application uses various FlashCONNECT API calls to create a Web page. When
the application returns to WWW-IRUN or calling w3Input, the Web page created
by the application is returned to FCService and FlashCONNECT notifies
FCService whether the connection is persistent or not.
• FCService passes the information back to fccgi.exe, fcisapi.dll, or FCServlet. If
the connection is not persistent, the connection is made available for another
user. If the connection is persistent, the connection is reserved and the timeout
period is started.
• fcisapi.dll, fccgi.exe, or FCServlet passes the page back to the Web server and
finishes.
• Web server passes the page back to the browser and finishes.
• Browser displays the new Web page.