Programs can use browsers to inspect and delete existing messages in shared durables.
More...
Programs can use browsers to inspect and delete existing messages in shared durables.
To create a browser object, see tibBrowser_Create.
This file defines browser calls.
#define TIB_BROWSER_PROPERTY_DOUBLE_PERSISTENCE_RETRY_DURATION "com.tibco.ftl.client.browser.persistence.retry.duration" |
Retry duration for browser operations; double.
When tibBrowser_Create or tibBrowser_DeleteMessage cannot access the persistence server (usually because of network failure or quorum unavailability), they can automatically retry the interaction. The value of this property overrides the retry behavior of the server. Supply it to the browser create call.
Values:
-
0 No retry. The call raises an exception.
-
-1 Synchronously retry the interaction until it succeeds. The call returns only upon success.
-
n (Any positive double value) Retry the interaction for n seconds. Return upon success or raise an exception after timeout.
Closing the realm or destroying the browser supersedes and cancels retry behavior.
This property does not apply to tibBrowser_Next.
#define TIB_BROWSER_PROPERTY_STRING_LABEL "com.tibco.ftl.client.browser.label" |
Property name for a browser label; string.
It is good practice to include this property in every browser create call. Monitoring data incorporates these labels so administrators can identify and distinguish among internal subscribers created on behalf of browsers. Use labels that reveal the unique role and identity of each durable within the application program.
When the browser label is present in the browser create call, the new browser assigns it as the label of its internal subscribers.
See tibBrowser_Create.
Retrieve the next message in the durable.
A browser starts at the first available message in the durable. Each call to this function advances the browser to the next available message.
The browser will not return messages that have been delivered to live subscribers. To browse every message it may be necessary to stop all subscribers on the durable.
Messages returned by the browser may be delivered to, and acknowledged by, live subscribers at any time.
If the connection to the persistence service is interrupted, or some other error occurs, the call will fail, regardless of any retry duration. When this happens, calls to this function will continue to fail until tibBrowser_Reset is called, or a new browser is created.
The library owns the message object, and may destroy it after the program calls tibBrowser_Next, tibBrowser_Reset, or tibBrowser_Close. Application code may take a copy of the message via tibMessage_MutableCopy.
- Parameters
-
e | The exception object captures information about failures. |
browser | The call retrieves the next message in the browser's durable. |
- Returns
- A message.
NULL
indicates no more data.