This document includes the new features, enhancements, and fixed issues for Hazelcast C++ Client 3.8 release.
TLS: C++ client can now use TLS encryption while communicating with the cluster. The TLS is configured via the SSLConfig which is now part of the ClientConfig. Different TLS/SSL protocols can also be configured. Only the Hazelcast IMDG Enterprise servers support TLS connection. Hence, if you enable the SSLConfig, make sure that the client is talking to a Hazelcast IMDG Enterprise server. Otherwise, the client will not be able to connect to the cluster. You can find more information regarding the TLS feature at the client documentation page: https://github.com/hazelcast/hazelcast-cpp-client/tree/v3.8#tls-feature. You can also check the example code at: https://github.com/hazelcast/hazelcast-cpp-client/tree/v3.8/examples/tls
IMap::sumbitToKey Async API: C++ client now supports async
IMap::submitToKeyAPI. A new
Futureobject is provided at the API. The future acts similar to
std::future. You can now make async calls and get the responses when you need it. You can find a sample code usage at this link: https://github.com/hazelcast/hazelcast-cpp-client/blob/v3.8/examples/distributed-map/entry-processor/main.cpp#L72
- Added missing Portable Reader/Writer read/writeUTF array. 
- Added the method
executeOnKeysfor IMap entry processor. 
- Added write/readUTFArray interface to Portable Writer/Reader. .
- Fixed the boolean array serialization bug. 
- writeChar array serialization fix. 
- Fix for Default Portable Writer and Reader being not supporting 64-bit long write on 32-bit platforms. 
- Fixed gcc 4.1.2 compilation warnings.