Characterising BEE
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 >> Characterising BEE <=  =>      <  1  >  
Characterising BEE Distinctive architecture of BEE

The architecture of BEE Script is characterised by the followings:

·         Pre-allocation of resources (CROFT – Customer Resource Online Facility Tables) based on the URL of the web page: Resource handles are completely concealed from the program code.  This design simplifies the coding for finding and binding the resources, and allows portability across servers and platforms.  As no resources are specified in the program code, different web pages can share the same piece of code or template with absolutely no modification.  (Please see "Virtual Page" for details.)

·         Security:  Because the program code has no access to the resource handles, a web page could never be able to access anything outside of its predefined Scope.  Even if an intruder with complete knowledge of the source code runs a modified script on the same physical server, he or she would not be able to access the same resources because the resources are allocated to the URL, not the page.  The binding of resources to the URL protects the web page from copy-modify-execute attacks.

·         Built-in multi-access-level authentication: Authentication settings and user data (login, passwords and other attributes) are bound to the URL and are subject to the same resource allocation protection under CROFT.  The authentication process is transparent to the program code, separating the role of the designer/developers and the security administrators.

·         Rich functionality: full cross-platform SQL database support, asynchronous remote function call, intrinsic support for e-mail generation, complete off-the-code program parameters registry (the "scheme" class), automatic web administrator's site, online content editing and "Virtual Page" generation, to name a few.

·         Adaptive syntax: Dual form of coding (BEE Script and BEE Tag) makes it flexible to mix with other web page constructs.  Attribute Name-Value Pair syntax provides non-positional parameter passing and makes the code robust and easy to extend.

·         Non-typed, multi-value and macro-style variable structure: All BEE Variables are implemented in array.  Value strings are evaluated recursively for BEE Variables (like string macro substitution), allowing straightforward nested-addressing and simplifying complicated symbolic referencing.

·         Well-defined variable hierarchy: The "class%name:element" structure provides a three-tier hierarchy.  "System Class" standardises variable usage and removes ambiguity resulted from various programming styles.  "Object Classes" provides an object-oriented programming environment for function encapsulation.

·         User extendable command set: There are only few dozen intrinsic commands and over half of them is common flow controls like declarations, conditionals, looping and debugging.  The rest are authentication, system control, database and specific functions like mail and text control.  Programmers can extend the functionality by defining functions, BEE Conversions and objects, which use the same calling syntax as the intrinsic features.

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