|
|
This Quick Start chapter describes the general usage of the Event Subscription Service (ESS). Apply this basic process when implementing the ESS in your client-source code.
Step 2 Compile the CiscoEventGateway.idl file with your IDL compiler to produce a version of the CiscoEventGateway module that is compatible with the target language of your client-source code.
Step 3 Use include or import directives, as appropriate, to ensure the target-language contents generated from your IDL files are available to your executable client-code for its ESS usage.
Step 4 Based on your event-handling scheme and the CiscoEventGateway::Event structure, design an algorithm for handling event data that is delivered to the CiscoEventGateway::Callback object through the in parameter of the CiscoEventGateway::Callback::deliverEvents() operation.
Step 5 Get an object reference to the CiscoEventGateway::EventGateway interface using the methods supplied with your CORBA implementation and using the target-language constructor methodology that applies to your client-source code.
Step 6 Create an instance of the CiscoEventGateway::Callback interface using the constructor methodology that applies to the target language of your client source code.
Step 7 Register your new CiscoEventGateway::Callback object with the Event Gateway server using the registration facilities supplied by the CiscoEventGateway::EventGateway interface, or reregister a previously registered CiscoEventGateway::Callback object with the Event Gateway server upon restarting the client application.
Step 8 Subscribe your CiscoEventGateway::Callback object to one or more subjects for which the ESS publishes information. At this point your client application begins receiving event notifications for the specified subject. Terminate subject subscriptions for each Callback object, as applicable.
Step 9 Destroy CiscoEventGateway::Callback objects—using the destructor methodology that applies to the IDL-mapped source language for your client application—when they becomes obsolete.
 |
Tips When planning your event-handling scheme, implement a persistent storage mechanism to track the unique identifiers returned by the CiscoEventGateway::EventGateway::registerCallback() operation for all active CiscoEventGateway::Callback objects. Upon restarting your client application, use the client-stored ID values as input parameters to the EventGateway::reregisterCallback() operation to reregister the corresponding Callback objects with the Event Gateway server. |
Posted: Fri Sep 22 20:09:14 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.