summaryrefslogtreecommitdiff
path: root/TAO/orbsvcs/orbsvcs/RtecEventComm.idl
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/orbsvcs/orbsvcs/RtecEventComm.idl')
-rw-r--r--TAO/orbsvcs/orbsvcs/RtecEventComm.idl38
1 files changed, 17 insertions, 21 deletions
diff --git a/TAO/orbsvcs/orbsvcs/RtecEventComm.idl b/TAO/orbsvcs/orbsvcs/RtecEventComm.idl
index 69c50b6409c..6e6e4282171 100644
--- a/TAO/orbsvcs/orbsvcs/RtecEventComm.idl
+++ b/TAO/orbsvcs/orbsvcs/RtecEventComm.idl
@@ -1,17 +1,16 @@
+//
// $Id$
+//
-#ifndef TAO_RTEC_EVENTCOMM_IDL
-#define TAO_RTEC_EVENTCOMM_IDL
-
-#include "TimeBase.idl"
+#include "CosTimeBase.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 ""
-module RtecEventComm
-{
+module RtecEventComm {
+
// = TITLE
// User defined Event Data.
//
@@ -25,13 +24,12 @@ module RtecEventComm
// sequence of octet.
typedef sequence<octet> EventPayload;
- struct EventData
- {
+ struct EventData {
long x;
long y;
double pad0;
- long pad1;
+ long pad1;
// This two objects ensure that the encapsulated stream below is
// properly aligned; this makes the decoding of the payload more
// efficient because we can use the usual demarshalling code
@@ -86,8 +84,8 @@ module RtecEventComm
//
// = DESCRIPTION
// Events are represented by this structure, it is simply a
- // header,data pair.
- //
+ // header,data pair.
+ //
EventHeader header;
EventData data;
@@ -95,17 +93,15 @@ module RtecEventComm
};
typedef sequence<Event> EventSet;
- interface PushConsumer
- {
- oneway void push (in EventSet data);
- void disconnect_push_consumer ();
- };
+ interface PushConsumer {
+ oneway void push (in EventSet data);
+ void disconnect_push_consumer();
+ };
- interface PushSupplier
- {
- void disconnect_push_supplier ();
- };
+ interface PushSupplier {
+ void disconnect_push_supplier();
+ };
};
-#endif /* TAO_RTEC_EVENTCOMM_IDL */
+