Method
Acknowledge messages.
The behavior of this call depends on the acknowledgement mode of the Session
.
ClientAcknowledge
mode, this call acknowledges all messages that the program has consumed within the session. (This behavior complies with the JMS specification.)ExplicitClientAcknowledge
mode, this call acknowledges only the individual message. (This mode and behavior are proprietary extensions, specific to TIBCO EMS.)ExplicitClientDupsOkAcknowledge
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.)Three events mark a message as consumedthat is, eligible for acknowledgment using this method:
EMSMessageHandler
event, it marks the message argument as consumed.IMessageListener.OnMessage
callback, it marks the message argument as consumed.receive
call returns a message, it marks that message as consumed.The server might redeliver unacknowledged messages.
TIBCO Enterprise Message Service™ .NET Reference System Release 4.3, February 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |