![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
tibems_status tibemsMsg_Acknowledge(tibemsMsg message );
message has usage pointer.
• In TIBEMS_CLIENT_ACKNOWLEDGE mode, this call acknowledges all messages that the program has consumed within the session. (This behavior complies with the JMS specification.)
• In TIBEMS_EXPLICIT_CLIENT_ACKNOWLEDGE mode, this call acknowledges only the individual message. (This mode and behavior are proprietary extensions, specific to TIBCO EMS.)
• In TIBEMS_EXPLICIT_CLIENT_DUPS_OK_ACKNOWLEDGE mode, this call lazily acknowledges only the individual message. Lazy means that the provider client library can delay transferring the acknowledgement to the server until a convenient time; meanwhile the server might redeliver the message. (This mode and behavior are proprietary extensions, specific to TIBCO EMS.)Two events mark a message as consumed—that is, eligible for acknowledgment using this function:
• Just before the provider calls an tibemsMsgCallback function, it marks the message argument as consumed.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |