ezAJAXEngine Behaviors
register_ezAJAX_function
One of the more powerful features of ezAJAX is the ability to queue-up specific units of processing which can be Server Commands or any other JavaScript statement(s).
Use the “oAJAXEngine.register_ezAJAX_function(s)” function to queue-up a unit of processing in the form of a String object instance that contains one or more valid JavaScript statement(s).
The ezAJAXEngine will attempt to process all the available queued-up processing units that are present whenever a block of data is received by the ezAJAXEngine.
This allows the programmer to do such things as simulate a series of client-side actions that are to be performed whenever the next block of data is received by the ezAJAXEngine. This can be quite useful when a series of client-side actions are to be performed as soon as the ezAJAXEngine receives the first block of data from the ezAJAX Server to kick-start some kind of processing or to enable GUI elements or some other type of processing.
This feature could also be used to queue-up ezAJAX Server Commands that may need to be queued-up while the Server is busy processing a prior Server Command.
The programmer could issue the “oAJAXEngine.isIdle()” function call to determine if the ezAJAXEngine instance is busy processing a prior Server Command. This could be done whenever a Server Command is about to be sent to the server in an asynchronous manner. This level of programmer would be considered quite advanced as most programmers will probably simply disable those GUI functions that cannot be performed while the ezAJAX Server is busy. In fact the programmer could simply queue-up function calls that enable GUI elements that need to be disabled while the ezAJAX Server is busy processing a Server Command.
Improved Error Handling in Version 0.91
The ezAJAXEngine Object instances will automatically react in a more robust manner whenever an error occurs in a Server Command Call-Back function.
Previously the behavior was to display a pop-up Error panel that did identify the error but did not specify the specific Call-Back that generated the error.
This level of error handling is only activated whenever a previously queued-up unit of processing encounters a JavaScript Error of some kind.
- ezAJAXEngine.browser_is_ff: This class variable returns “true” when the client browser is known to be a version of FireFox.
- ezAJAXEngine.browser_is_ie: This class variable returns “true” when the client browser is known to be a version of MSIE.
- ezAJAXEngine.browser_is_ns: This class variable returns “true” when the client browser is known to be a version of Netscape.
- ezAJAXEngine.browser_is_op: This class variable returns “true” when the client browser is known to be a version of Opera.
ezAJAXEngine.browserVersion()
This class method returns the client browser version in the form of a floating point value. For instance, MSIE 6.0 returns the value of “6.0”; FireFox 1.5.0.6 returns the value of “1.506”; Netscape 8.1 returns the value of “8.1” and Opera 9.1 returns the value of “9.1”.
ezAJAXEngine.isBrowserVersionCertified()
This class method returns “true” when the client browser is known to be fully functional from the perspective of ezAJAX otherwise “false” is returned.
ezAJAXEngine.browserCertificationCallback()
This Call-Back method is fired whenever the client browser is known to be outside the boundaries of those browsers that are known to be fully compatible with ezAJAX. The following browser versions are certified to work with ezAJAX: MSIE 6.0, FireFox 1.5.0.x, Netscape 8.x and Opera 9.x. No other browsers are known to be fully functional with ezAJAX, if you know your browser is fully functional with the current version of ezAJAX you may code your own Call-Back method to override the default behavior that pops-up a warning to let users know when their client browser is not known to be compatible with ezAJAX. | 
