![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBEMS_AUTO_ACKNOWLEDGE TIBEMS_CLIENT_ACKNOWLEDGE In this mode, the client program acknowledges receipt by calling tibemsMsg_Acknowledge on page 25. Each call acknowledges all messages received so far. TIBEMS_DUPS_OK_ACKNOWLEDGE As with TIBEMS_AUTO_ACKNOWLEDGE, the session automatically acknowledges messages. However, it may do so lazily.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. Lazy acknowledgement can reduce session overhead. TIBEMS_EXPLICIT_CLIENT_ACKNOWLEDGE As with TIBEMS_CLIENT_ACKNOWLEDGE, the client program acknowledges receipt by calling tibemsMsg_Acknowledge on page 25. However, each call acknowledges only the individual message. The client may acknowledge messages in any order. TIBEMS_EXPLICIT_CLIENT_DUPS_OK_ACKNOWLEDGE In this mode, the client program lazily acknowledges only the individual message, by calling tibemsMsg_Acknowledge on page 25. The client may acknowledge messages in any order.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. TIBEMS_NO_ACKNOWLEDGE In TIBEMS_NO_ACKNOWLEDGE mode, messages do not require acknowledgement (which reduces message overhead). The server never redelivers messages.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |