Inheritance diagram for code::EventCallback:
To use interprocess communication, make a subclass of EventCallback and implement the actionPerformed() function. The actionPerformedOnError function is recommended, but not required.
The callbacks need not be re-entrant.
Public Member Functions | |
virtual void | actionPerformed (const Buffer &msg)=0 |
This is the function that will be invoked when the event happens. | |
virtual void | actionPerformedOnError () |
This is the function that will be invoked when there is a system error making event notification not possible, either for the particular event requested or for all events. | |
virtual | ~EventCallback () |
Meant to be subclassed. |
virtual code::EventCallback::~EventCallback | ( | ) | [inline, virtual] |
Meant to be subclassed.
virtual void code::EventCallback::actionPerformed | ( | const Buffer & | msg | ) | [pure virtual] |
This is the function that will be invoked when the event happens.
Passed in to you is the message that was posted.
Additional arguments may be simply obtained by adding the appropriate arguments to your EventCallback subclass. (See for example, the more rounded LBEventCallback, which gives you access to the LB name used for update notification).
Implemented in code::SQLEventHandler::SQLEventCallback, and code::ActionListenerAdapter.
virtual void code::EventCallback::actionPerformedOnError | ( | ) | [inline, virtual] |
This is the function that will be invoked when there is a system error making event notification not possible, either for the particular event requested or for all events.
Additional arguments may be simply obtained by adding the appropriate arguments to your EventCallback subclass. (See for example, the more rounded LBEventCallback, which gives you access to the LB name used for update notification).