Connection Manager exposes Custom Events that track the progress of a transaction throughout its lifecycle. These Custom Events are raised at the global level and at the transaction level. The following code example provides a step-by-step approach to subscribing to transactional Custom Events raised by Connection Manager. In this scenario, an event handler object is created to handle all of the Custom Events; this event handler object is passed to Connection Manager in the callback object. Connection Manager will automatically subscribe to the events and fire the specified events.
Click "Send a Request" below to try it out, then read the description below to learn how to subscribe to transactional Custom Events in Connection Manager.
Create an object to handle all the custom events fired by Connection Manager.
Let's create two functions to provide handlers for
callback.failure compatibility. The inclusion of these handlers will demonstrate their backward compatibility with Custom Events.
Subscribe to the transaction custom events fired by Connection Manager by creating a
customevents object in the callback object. NOTE: callback.success and callback.failure are provided here to demonstrate backward compatibility, and would be redundant to customevents.onSuccess and customevents.onFailure, respectively.
YAHOO.util.Connect.asyncRequest to make a request to
get.php, and PHP will return the contents of
Each event handler in
transactionObject will be triggered in response to its custom event(e.g., transactionObject.start will be called when startEvent fires). In this example, event handlers are created and subscribed to all possible events raised by Connection Manager.
Note: Logging and debugging is currently turned off for this example.
All YUI 2.x users should review the YUI 2.8.2 security bulletin, which discusses a vulnerability present in YUI 2.4.0-2.8.1.