Chapter 2. FLY.PHP - RUNTIME EXECUTION WORKFLOW

Table of Contents

STEP 1: Set up environment variables
STEP 2: Including external files
STEP 3: Get the client IP addresss
STEP 4: Check the current client browser window
STEP 5: Start a new session if necessary
STEP 6: Fo non new sessions: take back session flow
STEP 7: Source code extraction and execution
STEP 8: Output by merging html template.
STEP 9: Serializing objects
STEP 10: Output error if any.

Every call from the browser to the HTTP server goes through the file called 'FLY.PHP'. This script manages the execution of the process within the NO-SOD Framework environment. By calling the FLY.PHP at every process of your web application, you take directly benefit of the framework security and integrated development environment.

Explanation step by step of the FLY process:

STEP 1: Set up environment variables

  • nsdmailing

    values = 0 (Inactive) or 1 (Active)

    When activated, every call to the mailing functions provided in the framework will be executed. Set this to 0 if you do not have mail infrastructure, such a SMTP server.

  • load

    values = 0 or 1 or 2

    This variable defines how the framework will find the source code and html files reuired during a module execution.

    • 0 means use the web server file system
    • 1 means use the system database
    • 2 means use the web server development file system.

    The major difference between load 0 and 2, is that with load 2, the documents loaded are not kept in memory for next calls.

    This is easier to develop or debug in load 2, avoiding to logoff from the moduleat each trial. This is correct for all document types execept LIB files. LIB files are always kept in memory.

  • nsdsqltrace

    values = 0 (Inactive) or 1 (Active)

    When activated, the framework genrates SQL logs of every database access under the /logs directory.

  • nsdver

    This set the framework version. It's used to retrieve LIB, INC, SRC and HTML files of the current framework at runtime.

  • nsddspz

    This is the final output variable. Developers set this variable to the name of their html file to output, within the SRC code.

    The FLY will use this variable in one of the latest step to see if there is an output to process or not.