tibems_status tibemsMsgConsumer_Close(tibemsMsgConsumer msgConsumer );
msgConsumer has usage pointer.
If a receive call or a message listener callback is in progress, then this function waits until that call returns, and then closes the consumer.This call also notifies the server that the client program is closing the consumer. In response, the server stops sending message data to the consumer.tibems_status tibemsMsgConsumer_GetDestination(tibemsMsgConsumer msgConsumer,tibemsDestination* destination );
msgConsumer and destination have usage pointer.
Programs set this destination when creating the consumer, and cannot subsequently change it.tibems_status tibemsMsgConsumer_GetMsgListener(tibemsMsgConsumer msgConsumer,tibemsMsgCallback* callbackPtr,
The function stores a pointer to the closure data in this location. This pointer is passed into the message listener callback.EMS C programs can implement a message listener as a callback function paired with closure data. This call extracts these items from a consumer object.Your program implements the callback, and registers it by calling tibemsMsgConsumer_SetMsgListener. When a message arrives, the consumer calls the callback.tibems_status tibemsMsgConsumer_GetMsgSelector(tibemsMsgConsumer msgConsumer,
msgConsumer and selectorPtr have usage pointer.
A message selector restricts the set of messages that the consumer receives to those that match the selector; see Message Selectors.Programs can set this property only when creating the consumer object; see tibemsSession_CreateConsumer on page 293.tibems_status tibemsMsgConsumer_GetNoLocal(tibemsMsgConsumer msgConsumer,tibems_bool* noLocal );
msgConsumer has usage pointer.
When true, the consumer does not receive messages sent through the same server connection (that is, the connection associated with the consumer).tibems_status tibemsMsgConsumer_Receive(tibemsMsgConsumer msgConsumer,tibemsMsg* message );
msgConsumer and message have usage pointer.
• If a message arrives at the destination, this call immediately consumes that message and returns.When calling tibemsMsgConsumer_Receive from a transaction, the consumer retains the message until transaction commits.tibems_status tibemsMsgConsumer_ReceiveNoWait(tibemsMsgConsumer msgConsumer,tibemsMsg* message);
msgConsumer and message have usage pointer.
When the destination has at least one message ready, this function immediately returns the next message.When the destination does not have any messages ready, this function immediately returns TIBEMS_NOT_FOUND.When calling receiving within a transaction, the consumer retains the message until transaction commits.tibems_status tibemsMsgConsumer_ReceiveTimeout(tibemsMsgConsumer msgConsumer,tibemsMsg* message,tibems_long timeout );
msgConsumer and message have usage pointer.
When present, wait no longer than this interval (in milliseconds) for a message to arrive. Zero is a special value, which specifies no timeout (block indefinitely).This function consumes the next message from the consumer’s destination. When the destination does not have any messages ready, this function blocks:
• If a message arrives at the destination, this call immediately consumes that message and returns.When calling receive within a transaction, the consumer retains the message until transaction commits.tibems_status tibemsMsgConsumer_SetMsgListener(tibemsMsgConsumer msgConsumer,tibemsMsgCallback callback,
EMS C programs can implement a message listener as a callback function paired with closure data. This call sets these items in a consumer object.Your program implements the callback, and registers it by calling this function. When a message arrives, the consumer calls the callback.
Copyright © TIBCO Software Inc. All Rights Reserved.