diff options
Diffstat (limited to 'TAO/orbsvcs/orbsvcs/RtecEventComm.idl')
-rw-r--r-- | TAO/orbsvcs/orbsvcs/RtecEventComm.idl | 100 |
1 files changed, 0 insertions, 100 deletions
diff --git a/TAO/orbsvcs/orbsvcs/RtecEventComm.idl b/TAO/orbsvcs/orbsvcs/RtecEventComm.idl deleted file mode 100644 index 3b0a636165a..00000000000 --- a/TAO/orbsvcs/orbsvcs/RtecEventComm.idl +++ /dev/null @@ -1,100 +0,0 @@ -// $Id$ - -#ifndef TAO_RTEC_EVENTCOMM_IDL -#define TAO_RTEC_EVENTCOMM_IDL - -#include "TimeBase.idl" - -// Remove the prefix definition... -// @@ TODO Is this the "Right Thing"? AFAIK the spec does not mention -// if pragmas should survive the file scope... -#pragma prefix "" - -#include "RtecDefaultEventData.idl" - -module RtecEventComm -{ - // = TITLE - // User defined Event Data. - // - // = DESCRIPTION - // The Event payload is defined by this type. - // Users wanting maximum flexibility can use an Any, - // users that only have one type of event may use structures, - // other users may preffer union, trying to strike a balance - // between performance and flexibility. - // Users willing to implement their own marshalling may use a - // sequence of octet. - - typedef RtecEventData EventData; - - typedef TimeBase::TimeT Time; - - typedef long EventSourceID; - typedef long EventType; - - struct EventHeader - { - // = TITLE - // The Event Header - // - // = DESCRIPTION - // Each event carries some information to do filtering, - // correlation, etc. - EventType type; - // The event type. - // This may be different from the discriminator in the EventData - // union above, the motivation is to allow filtering by data - // contents: different event types are assigned to different data - // contents though they use the same discriminator. - - EventSourceID source; - // Some way to identify the supplier. - - long ttl; - // The "Time To Live" count, each time an EC process the event it - // decreases the TTL field, when it gets to zero the message is no - // longer forwarded. - - Time creation_time; - // A time value, the name is a bit misleading, it is used for - // timestamping but also used to setup timers in the consumer - // subscriptions. -#if !defined (TAO_LACKS_EVENT_CHANNEL_TIMESTAMPS) - Time ec_recv_time; - Time ec_send_time; - // Some timestamps, they actually belong in the payload, for some - // kind of measument event. -#endif /* TAO_LACKS_EVENT_CHANNEL_TIMESTAMPS */ - }; - - struct Event - { - // = TITLE - // The Event structure. - // - // = DESCRIPTION - // Events are represented by this structure, it is simply a - // header,data pair. - // - EventHeader header; - - EventData data; - // The event payload. - }; - typedef sequence<Event> EventSet; - - interface PushConsumer - { - oneway void push (in EventSet data); - void disconnect_push_consumer (); - }; - - interface PushSupplier - { - void disconnect_push_supplier (); - }; - -}; - -#endif /* TAO_RTEC_EVENTCOMM_IDL */ |