 |
Tango Core Classes Reference
9.3.3
|
|
Tango Core Classes Reference
9.3.3
|
Event and asynchronous (callback model) calls base class. More...
#include "tango.h"
Public Member Functions | |
| virtual void | attr_read (AttrReadEvent *are) |
| Asynchronous read attribute execution callback method. More... | |
| virtual void | attr_written (AttrWrittenEvent *awe) |
| Asynchronous write attribute execution callback method. More... | |
| virtual void | cmd_ended (CmdDoneEvent *cde) |
| Asynchronous command execution callback method. More... | |
| virtual void | push_event (AttrConfEventData *ace) |
| attribute configuration change event callback method More... | |
| virtual void | push_event (DataReadyEventData *dre) |
| Data ready event callback method. More... | |
| virtual void | push_event (DevIntrChangeEventData *dic) |
| Device interface change event callback method. More... | |
| virtual void | push_event (EventData *ed) |
| Event callback method. More... | |
| virtual void | push_event (PipeEventData *ped) |
| Pipe event callback method. More... | |
Event and asynchronous (callback model) calls base class.
When using the event push model (callback automatically executed), there are some cases (same callback used for events coming from different devices hosted in device server process running on different hosts) where the callback method could be executed concurently by different threads started by the ORB. The user has to code his callback method in a thread safe manner.
$Author$ $Revision$
|
inlinevirtual |
Asynchronous read attribute execution callback method.
This method is defined as being empty and must be overloaded by the user when the asynchronous callback model is used. This is the method which will be executed when the server reply from a read_attribute(s) is received in both push and pull sub-mode.
| are | The read attribute data |
|
inlinevirtual |
Asynchronous write attribute execution callback method.
This method is defined as being empty and must be overloaded by the user when the asynchronous callback model is used. This is the method which will be executed when the server reply from a write_attribute(s) is received in both push and pull sub-mode.
| awe | The write attribute data |
|
inlinevirtual |
Asynchronous command execution callback method.
This method is defined as being empty and must be overloaded by the user when the asynchronous callback model is used. This is the method which will be executed when the server reply from a command_inout is received in both push and pull sub-mode.
| cde | The command data |
|
inlinevirtual |
attribute configuration change event callback method
This method is defined as being empty and must be overloaded by the user when events are used. This is the method which will be executed when the server send attribute configuration change event(s) to the client.
| ace | The attribute configuration change event data |
|
inlinevirtual |
Data ready event callback method.
This method is defined as being empty and must be overloaded by the user when events are used. This is the method which will be executed when the server send attribute data ready event(s) to the client.
| dre | The data ready event data |
|
inlinevirtual |
Device interface change event callback method.
This method is defined as being empty and must be overloaded by the user when events are used. This is the method which will be executed when the server send device interface change event(s) to the client.
| dic | The device interface change event data |
|
inlinevirtual |
Event callback method.
This method is defined as being empty and must be overloaded by the user when events are used. This is the method which will be executed when the server send event(s) to the client.
| ed | The event data |
|
inlinevirtual |
Pipe event callback method.
This method is defined as being empty and must be overloaded by the user when events are used. This is the method which will be executed when the server send pipe event(s) to the client.
| ped | The pipe event data |
1.8.16