How BEE runs
Username:  
Password:
  > Home
> User Guide
v Reference
    v Introduction
       o How to use this doc
       o Background
       > Design Principles
       o Characterising BEE
       o How BEE runs
       o What is a BEE Web Site
    > CROFT
    > BEE Variables
    > BEE Syntax
    > BEE Commands
    > Database Operation
    > Content Management
    > Objects and Classes
    > Interface with others
    o Glossary
> Portal Object
> Development Guide


Shortcuts
sys Class
debug Class
Intrinsic Conversions
>> Reference >> Introduction >> How BEE runs <=  =>      <  1  >  
How BEE runs How a BEE application is executed

BEE is built on three pillars:

1)      CROFT for resource allocation, authentication and permanent settings

2)      BEE Script/Tag Compiler

3)      BEE Run-time Library

The web designer and programmer create the web site and upload the web pages onto the BEE enabled web server.  The server upon receiving the web pages will scan for BEE Script statements and convert them into BEE Tags.  The web pages are then compiled into the target implementation codes (PHP at the moment) and stored in the web storage.

At run-time, the implementation codes will be called on to perform the intended function of the BEE commands.  Most of these functions however are implemented as in the BEE Run-time Library, which access CROFT implicitly if resources are required.  That is the resource will be identified and opened upon its first use.

Previous Page       Next Page

Accsoft Computer Technology Pty Ltd     ABN: 98 065 617 549
PO Box 892, Epping NSW 1710         Level 1, Epping Office Park, 242 Beecroft Rd, Epping NSW 2121, Australia
Tel: Sydney - (02)98691668     National - 1300-881668         Fax: (02)98691866
© Copyright 2003 Accsoft Computer Technology Pty Ltd