#include "ace/Message_Block.h"#include "orbsvcs/Time_Utilities.h"Include dependency graph for Event_Service_Constants.h:

This graph shows which files directly or indirectly include this file:

Keep constants required by both Event Service implementation and the Scheduling Service implementation.
|
|
ACE_ES_DISPATCHING_MODULE determines what Dispatching Module is used by the channel. ACE_ES_Dispatching_Base is a null dispatcher that can be used to build an EFD. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is the chunk size of the cached allocator for ACE_ES_Event_Container. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Max number of consumers that one supplier can have subscribed to one type of event (including source-only). This restriction is very lightweight since subscription lists are dynamic. This constant is only used for ACE_ES_Simple_Set in Event_Channel.* for disconnecting consumers. Since these objects are allocated off the stack, we can increase this number without requiring more heap memory. |
|
|
This is the number of events a consumer can subscribe to.
|
|
|
|
|
|
|
|
|
Max preemption priority.
|
|
|
The max number of priorities provided by the target platform. |
|
|
Initial value: This is the maximum sub priority.
|
|
|
Initial value: The minimum preemption priority.
|
|
|
Initial value: This is the minimum sub priority.
|
|
|
Initial value: {
250000,
500000,
1000000,
2000000,
10000000
} |
|
|
This is the number of threads spawned for *each* priority queue in the channel's Dispatching Module. This is used by the channel when creating the dispatch module. |
1.2.18