Guaranteed Message Flows
For a client application to publish Guaranteed messages to or consume Guaranteed messages from Solace, it must create one or more flows within a session. A flow is an API object that allows applications to send or receive Guaranteed messages.
A subscriber flow allows applications to receive Guaranteed messages from an endpoint, such as a queue. Unless otherwise noted, references to flows are to subscriber flows.
Clients also use flows when they publish Guaranteed messages. For the Solace Java RTO API, Solace C API, Solace JavaScript API, Solace Node.js API, and Solace .NET API, a producer flow is automatically established at the beginning of a session. This allows the client to send persistent messages at any time while the session remains active. For more information, see Publishing Guaranteed Messages.
| Solace Messaging API | Use |
|---|---|
|
Solace Java RTO API |
|
|
Solace C API |
|
|
Solace .NET API |
|
|
Solace JavaScript API and Solace Node.js API |
|
Browsers
A browser allows client applications to look at messages spooled on queues from oldest to newest without removing them. After messages are browsed, they can still be received by consumers over flows.
It is also possible to use a browser to look at messages and selectively remove them from the queue. Removed messages can no longer be consumed.
In the Solace .NET API, browsers are objects. In the Solace Java RTO API and Solace C API, flows can act as browsers when a specific FlowHandle or flow property is set.
The Solace JavaScript API and Solace Node.js API do not support message browsing.
| Solace Messaging API | Use |
|---|---|
|
Solace Java RTO API |
|
|
Solace C API |
|
|
Solace .NET API |
|
|
Solace JavaScript API and Solace Node.js API |
Not applicable |