Version 1.1.2

Examples now include a '-trust' cmd line option in order to reference the directory containing the Solace supplied .pem file, which is used to connect to a secure SMF host. No API changes. Code uses a solace session property SESSION_SSL_TRUST_STORE_DIR which could have previously been set using the existing API.

Version 1.1.1

init call was returning incorrect error code on connection failure - now fixed

Version 1.1.0

Ability to get different Solace message payload types:

Current callbacks for new messages give the binary payload to the registered func

• setTopicMsgCallback
• setQueueMsgCallback

New alternative methods give Q the msg on their registered callback functions (instead of the binary payload parameter)

• setTopicRawMsgCallback
• setQueueRawMsgCallback

When the user it given the msg, they can call one of the following to get the payload

• getPayloadAsXML
• getPayloadAsString
• getPayloadAsBinary

This isnt about us transforming the data, but how Solace encodes and stores data in the msgs - each of these calls a corresponding solace C call to get the XML/string/binary data (i.e. the solace string works when the sender has sent a solace string type message).
An example of this style is now shown in examples/sol_sub_direct.q

Initial stable release

Promoting 1.0.0-rc.1 to 1.0.0

Release candidate update, Rhel7 release fix, repo structure + build standardised

• .travis.yml being used standardised with MQTT/HDF5/prometheus-exporter
• Update to structure of repo script/ -> q/, source/ -> src/
• Linux release now built on trusty linux distribution rather than xenial, this will allow release to be used with Rhel7, closes #152

Initial release candidate for version 1.0.0

First release.