DlsInfo

typedef struct dlist_node { struct dlist_node *next;   /**< next pointer */ struct dlist_node *prev;   /**< previous pointer */ } DlistNode;

typedef enum {     DLS_NOT_RUNNING=0,  /**< not running */     DLS_LAUNCHED=1,     /**< launched, but waiting for confirmation */     DLS_RUNNING=2,      /**< fully up and running. */     DLS_TERMINATE_REQUESTED=3 /**< Requested termination, but waiting for confirmation. */ } DlsState;

typedef struct eoc_msg_header {     EocMsgType  type;  /**< specifies what message this is. */     EocEntityId src;   /**< EocEntityId of the sender. */     EocEntityId dst;   /**< EocEntityId of the receiver. */     union     {         UINT16 all;     /**< All 16 bits of the flags at once. */         struct         {             UINT16 event:1;    /**< This is a event msg. */             UINT16 request:1;  /**< This is a request msg. */             UINT16 response:1; /**< This is a response msg. */             UINT16 requeue:1;  /**< Tell eocmonitor to send this msg back to sender. */             UINT16 bounceIfNotRunning:1; /**< Do not launch the app to receive this message if                                                                         *  it is not already running. */             UINT16 unused:11;  /**< For future expansion. */         } bits;     } flags;  /**< Modifiers to the type of message. */     UINT16 sequenceNumber;     /**< "Optional", but read the explanation below.                                                     *                                                     * Senders of request or event message types                                                     * are free to set this to whatever                                                     * they want, or leave it unitialized.  Senders                                                     * are not required to increment the sequence                                                     * number with every new message sent.                                                     * However, response messages must                                                      * return the same sequence number as the                                                     * request message.                                                     *                                                      */     struct eoc_msg_header *next;   /**< Allows EocMsgHeaders to be chained. */     UINT wordData;   /**< As an optimization, allow one word of user                                     *   data in msg hdr.                                     *                                     * For messages that have only one word of data,                                     * we can just put the data in this field.                                     * One good use is for response messages that just                                     * need to return a status code.  The message type                                     * determines whether this field is used or not.                                     */     UINT dataLength; /**< Amount of data following the header.  0 if no additional data. */ } EocMsgHeader;