[TIBCO.EMS .NET client library 5.1 documentation]
Assembly: TIBCO.EMS (in TIBCO.EMS.dll)
Enumerate constants associated with sessions.
Namespace:
TIBCO.EMSAssembly: TIBCO.EMS (in TIBCO.EMS.dll)
Syntax
public enum SessionMode |
Public Enumeration SessionMode |
public enum class SessionMode |
Members
Member name | Description | |
---|---|---|
SessionTransacted | The session is transacted.
The IsTransacted property has this value if the session uses transaction semantics.
See SESSION_TRANSACTED
for more information.
| |
AutoAcknowledge | Automatic acknowledgment.
See AUTO_ACKNOWLEDGE for more information. | |
ClientAcknowledge | Client acknowledgment.
See CLIENT_ACKNOWLEDGE
for more information. | |
DupsOkAcknowledge | Duplication ok acknowledgment. See DUPS_OK_ACKNOWLEDGE
for more information. | |
NoAcknowledge |
Defines no acknowledge acknowledge mode.
This acknowledge mode
is a proprietary extension and when used offers increased performance
of the message consumers. Messages delivered to the sessions using
this acknowledge mode do not require acknowledgement and are
never redelivered regardless if the delivery has been successfull or not.
This can only be used by Topic sessions but not by Queue sessions.
See NO_ACKNOWLEDGE for more information.
| |
ExplicitClientAcknowledge |
Defines explicit client acknowledge mode.
This acknowledge mode is a proprietary extension.
Sessions using this acknowledge mode must acknowledge each message
explicitly calling the acknowledge() method for all messages.
The application can call aknowledge() in any order.
The general rule that acknowledging a
message will acknowledge all previous messages does not apply.
See EXPLICIT_CLIENT_ACKNOWLEDGE
for more information.
| |
ExplicitClientDupsOkAcknowledge |
Defines explicit client acknowledge mode with dups_ok.
This acknowledge mode is a proprietary extension. This acknowledge mode
implements the same explicit acknowledge logic as
the ExplicitClientAcknowledge mode. However while
ExplicitClientAcknowledge guarantees the success
of the acknowledge operation upon return, this mode does not
and, similarly to DupsOkAcknowledge mode, acknowledges message
lazily with the possibility that some acknowledged messages
may be redelivered. Like for ExplicitClientAcknowledge, this mode
requires an application to explicitly call acknowledge() method,
in any order, for each message it wants to acknowledge.
See EXPLICIT_CLIENT_DUPS_OK_ACKNOWLEDGE
for more information.
|