AWS IoT Device SDK C++ v2
1.34.0
AWS IoT Device SDK C++ v2
|
#include <Api.h>
Classes | |
struct | Version |
Static Public Member Functions | |
static Io::ClientBootstrap * | GetOrCreateStaticDefaultClientBootstrap () |
static Io::EventLoopGroup * | GetOrCreateStaticDefaultEventLoopGroup () |
static Io::HostResolver * | GetOrCreateStaticDefaultHostResolver () |
A singleton object representing the init/cleanup state of the entire CRT. It's invalid to have more than one active simultaneously and it's also invalid to use CRT functionality without one active.
|
noexcept |
Customize the ApiAllocator(), which is be used by any objects constructed without an explicit allocator.
|
noexcept |
Aws::Crt::ApiHandle::~ApiHandle | ( | ) |
|
delete |
|
delete |
ApiHandle::Version Aws::Crt::ApiHandle::GetCrtVersion | ( | ) | const |
Gets the version of the AWS-CRT-CPP library
|
static |
Gets the static default ClientBootstrap, creating it if necessary.
This default will be used when a ClientBootstrap is not explicitly passed but is needed to allow the process to function. An example of this would be in the MQTT connection creation workflow. The default ClientBootstrap will use the default EventLoopGroup and HostResolver, creating them if necessary.
The default ClientBootstrap will be automatically managed and released by the API handle when it's resources are being freed, not requiring any manual memory management.
|
static |
Gets the static default EventLoopGroup, creating it if necessary.
This default will be used when a EventLoopGroup is not explicitly passed but is needed to allow the process to function. An example of this would be in the MQTT connection creation workflow.
The EventLoopGroup will automatically pick a default number of threads based on the system. You can manually adjust the number of threads being used by creating a EventLoopGroup and passing it through the SetDefaultEventLoopGroup function.
The default EventLoopGroup will be automatically managed and released by the API handle when it's resources are being freed, not requiring any manual memory management.
|
static |
Gets the static default HostResolver, creating it if necessary.
This default will be used when a HostResolver is not explicitly passed but is needed to allow the process to function. An example of this would be in the MQTT connection creation workflow.
The HostResolver will be set to have a maximum of 8 entries by default. You can manually adjust the maximum number of entries being used by creating a HostResolver and passing it through the SetDefaultEventLoopGroup function.
The default HostResolver will be automatically managed and released by the API handle when it's resources are being freed, not requiring any manual memory management.
void Aws::Crt::ApiHandle::InitializeLogging | ( | LogLevel | level, |
const char * | filename | ||
) |
Initialize logging in awscrt.
level | Display messages of this importance and higher. LogLevel.NoLogs will disable logging. |
filename | Logging destination, a file path from the disk. |
void Aws::Crt::ApiHandle::InitializeLogging | ( | LogLevel | level, |
FILE * | fp | ||
) |
Initialize logging in awscrt.
level | Display messages of this importance and higher. LogLevel.NoLogs will disable logging. |
fp | The FILE object for logging destination. |
void Aws::Crt::ApiHandle::SetBYOCryptoClientTlsCallback | ( | Io::NewClientTlsHandlerCallback && | callback | ) |
BYO_CRYPTO: set callback for creating a ClientTlsChannelHandler. If using BYO_CRYPTO, you must call this prior to creating any client channels in the application.
void Aws::Crt::ApiHandle::SetBYOCryptoNewMD5Callback | ( | Crypto::CreateHashCallback && | callback | ) |
BYO_CRYPTO: set callback for creating MD5 hashes. If using BYO_CRYPTO, you must call this.
void Aws::Crt::ApiHandle::SetBYOCryptoNewSHA1Callback | ( | Crypto::CreateHashCallback && | callback | ) |
BYO_CRYPTO: set callback for creating SHA1 hashes. If using BYO_CRYPTO, you must call this.
void Aws::Crt::ApiHandle::SetBYOCryptoNewSHA256Callback | ( | Crypto::CreateHashCallback && | callback | ) |
BYO_CRYPTO: set callback for creating SHA256 hashes. If using BYO_CRYPTO, you must call this.
void Aws::Crt::ApiHandle::SetBYOCryptoNewSHA256HMACCallback | ( | Crypto::CreateHMACCallback && | callback | ) |
BYO_CRYPTO: set callback for creating Streaming SHA256 HMAC objects. If using BYO_CRYPTO, you must call this.
void Aws::Crt::ApiHandle::SetBYOCryptoTlsContextCallbacks | ( | Io::NewTlsContextImplCallback && | newCallback, |
Io::DeleteTlsContextImplCallback && | deleteCallback, | ||
Io::IsTlsAlpnSupportedCallback && | alpnCallback | ||
) |
BYO_CRYPTO: set callbacks for the TlsContext. If using BYO_CRYPTO, you need to call this function prior to creating a TlsContext.
newCallback | Create custom implementation object, to be stored inside TlsContext. Return nullptr if failure occurs. |
deleteCallback | Destroy object that was created by newCallback. |
alpnCallback | Return whether ALPN is supported. |
void Aws::Crt::ApiHandle::SetShutdownBehavior | ( | ApiHandleShutdownBehavior | behavior | ) |
Configures the shutdown behavior of the api handle instance
behavior | desired shutdown behavior |