|
AdventNet Web NMS 4 DMS API Specification | ||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||
As the amount of data transfered through the communication framework is large, various priorities with IDs are defined to control the data flow according to requirements. These IDs can direct the framework to send the data immediately or to add the data in queue to send later, as defined. When the DataObject is sent through the communication framework, DataPriorityID will be read and the data will be sent accordingly. It is upto the user to decide the priority of the data to be sent.
| Field Summary | |
static int |
HIGHPRIORITY
The data from the module with this priority will be stored in the high priority buffer and it will sent by a scheduler regularly based on the write interval configured. |
static int |
HIGHPRIORITY_SEND_IMMEDIATE
The data from the module with this priority will be stored in the high priority buffer and a scheduler will be started immediately for sending the data available in the high priority buffer to the Central Server. |
static int |
LOWPRIORITY
The data from the module with this priority will be stored in the low priority buffer and it will sent by a scheduler regularly based on the write interval configured. |
static int |
SEND_IMMEDIATE_WITHOUT_STORE
The data from the module with this priority will be sent to the Central Server immediately without being stored in the buffer. |
| Field Detail |
public static final int SEND_IMMEDIATE_WITHOUT_STORE
public static final int HIGHPRIORITY_SEND_IMMEDIATE
public static final int HIGHPRIORITY
public static final int LOWPRIORITY
|
AdventNet Web NMS 4 DMS API Specification | ||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||