Creating Temporary Endpoints
A client can consume Guaranteed messages from a temporary endpoint (a temporary queue or a non-durable topic endpoint). However, a temporary endpoint is non‑durable because it only exists as for as long as the session that it was created in.
Solace Messaging API for Java RTO, C, and .NET
Temporary queues and non‑durable topic endpoints are dynamically provisioned when a flow is created (the flow property SOLCLIENT_FLOW_PROP_BIND_ID sets the endpoint type, and SOLCLIENT_FLOW_PROP_DURABLE sets the endpoint durability).
Solace JavaScript API and Solace Node.js API
Temporary queues and non-durable topic endpoints are dynamically provisioned when a solace.MessageConsumer is created (the MessageConsumer property queueDescriptor defines the endpoint type and durability).
Related Samples
For an example of how to dynamically create temporary queues, see the SimpleFlowToQueue sample for the Solace Java RTO API and Solace .NET API.
For an example of how to dynamically create temporary topic endpoints, see the SimpleFlowToTopic sample for the Solace Java RTO API and Solace .NET API.
For the Solace JavaScript API and Solace Node.js API, see the GuaranteedReplier and GuaranteedRequestor samples.
| Solace Messaging API | Use |
|---|---|
|
Solace Java RTO API |
For temporary queues:
For non-durable Topic Endpoints:
|
|
Solace C API |
|
|
Solace .NET API |
For temporary queues:
For non-durable topic endpoints:
|
|
Solace JavaScript API and Solace Node.js API |
The |