Solace C API

The Solace Messaging API for C, version 7.33.0 (also referred to as SolClient), is specifically designed to provide high message throughput and low latency with the lowest CPU utilization possible. In addition to the common Enterprise API features, the Solace C API enables fine-grained control of threading and message processing through additional features:

• Allows fine-tuning of API behavior, such as whether operations should be blocking or non-blocking in nature.
• Allows for the option of application file descriptors to be monitored within the API, providing the application with callbacks for readable and writable events.
• Allows for the option of the application taking over control of file descriptors created within the API to connect to event brokers, where the application must provide readable and writable events to the API.
• Support for timer services.

The Solace C API supports the following Message Exchange Patterns:

• Publish-Subscribe
• Point-to-Point
• Request-Reply

 

Support for Solaris/SunOS is now deprecated and the last release was v7.23.0 (September 2022). For more information, see Deprecated Features.

Get Started

To get up to speed quickly developing applications using the Solace C API you may want to check out our C API Tutorials.

Before you can start working with the Solace C API, you must have access to a Solace event broker to test and use your C application.

You can get started using a Solace event broker in any of these ways:

• If you have an appliance event broker or software event broker already deployed, obtain
  • the hostname or IP address of an event broker to test against
  • a username and password to access it
  • a Message VPN in which you can produce and consume messages
• You can set up a software event broker as a container image. For more information, see Setting Up Container Images. 
• If you have Solace Cloud, you create a new event broker service. For more information, see Creating Event Broker Services.