AuthAzureStorage Unicode C Reference Documentation
Current Version: 188.8.131.52
Provides functionality for authenticating calls to Azure Storage Services.
HCkAuthAzureStorageW instance = CkAuthAzureStorageW_Create(); // ... CkAuthAzureStorageW_Dispose(instance);
Creates an instance of the HCkAuthAzureStorageW object and returns a handle ("void *" pointer). The handle is passed in the 1st argument for the functions listed on this page.
Objects created by calling CkAuthAzureStorageW_Create must be freed by calling this method. A memory leak occurs if a handle is not disposed by calling this function. Also, any handle returned by a Chilkat "C" function must also be freed by the application by calling the appropriate Dispose method, such as CkAuthAzureStorageW_Dispose.
void CkAuthAzureStorageW_putAccessKey(HCkAuthAzureStorageW cHandle, const wchar_t *newVal);
const wchar_t *CkAuthAzureStorageW_accessKey(HCkAuthAzureStorageW cHandle);
A valid base64 access key for the Azure storage account.
void CkAuthAzureStorageW_putAccount(HCkAuthAzureStorageW cHandle, const wchar_t *newVal);
const wchar_t *CkAuthAzureStorageW_account(HCkAuthAzureStorageW cHandle);
The Azure storage account name. (A storage account can contain zero or more containers. A container contains properties, metadata, and zero or more blobs. A blob is any single entity comprised of binary data, properties, and metadata. )top
void CkAuthAzureStorageW_putDebugLogFilePath(HCkAuthAzureStorageW cHandle, const wchar_t *newVal);
const wchar_t *CkAuthAzureStorageW_debugLogFilePath(HCkAuthAzureStorageW cHandle);
If set to a file path, causes each Chilkat method or property call to automatically append it's LastErrorText to the specified log file. The information is appended such that if a hang or crash occurs, it is possible to see the context in which the problem occurred, as well as a history of all Chilkat calls up to the point of the problem. The VerboseLogging property can be set to provide more detailed information.
This property is typically used for debugging the rare cases where a Chilkat method call hangs or generates an exception that halts program execution (i.e. crashes). A hang or crash should generally never happen. The typical causes of a hang are:
- a timeout related property was set to 0 to explicitly indicate that an infinite timeout is desired,
- the hang is actually a hang within an event callback (i.e. it is a hang within the application code), or
- there is an internal problem (bug) in the Chilkat code that causes the hang.
const wchar_t *CkAuthAzureStorageW_lastErrorHtml(HCkAuthAzureStorageW cHandle);
Provides information in HTML format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.top
const wchar_t *CkAuthAzureStorageW_lastErrorText(HCkAuthAzureStorageW cHandle);
Provides information in plain-text format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.top
const wchar_t *CkAuthAzureStorageW_lastErrorXml(HCkAuthAzureStorageW cHandle);
Provides information in XML format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.top
void CkAuthAzureStorageW_putLastMethodSuccess(HCkAuthAzureStorageW cHandle, BOOL newVal);
Indicate whether the last method call succeeded or failed. A value of TRUE indicates success, a value of FALSE indicates failure. This property is automatically set for method calls. It is not modified by property accesses. The property is automatically set to indicate success for the following types of method calls:
- Any method that returns a string.
- Any method returning a Chilkat object, binary bytes, or a date/time.
- Any method returning a standard boolean status value where success = TRUE and failure = FALSE.
- Any method returning an integer where failure is defined by a return value less than zero.
Note: Methods that do not fit the above requirements will always set this property equal to TRUE. For example, a method that returns no value (such as a "void" in C++) will technically always succeed.top
void CkAuthAzureStorageW_putScheme(HCkAuthAzureStorageW cHandle, const wchar_t *newVal);
const wchar_t *CkAuthAzureStorageW_scheme(HCkAuthAzureStorageW cHandle);
Can be "SharedKey" or "SharedKeyLite". The default value is "SharedKey".top
void CkAuthAzureStorageW_putService(HCkAuthAzureStorageW cHandle, const wchar_t *newVal);
const wchar_t *CkAuthAzureStorageW_service(HCkAuthAzureStorageW cHandle);
Can be "Blob", "Queue", "File", or "Table". The default is "Blob".top
void CkAuthAzureStorageW_putVerboseLogging(HCkAuthAzureStorageW cHandle, BOOL newVal);
If set to TRUE, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is FALSE. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.top
const wchar_t *CkAuthAzureStorageW_version(HCkAuthAzureStorageW cHandle);
Version of the component/library, such as "184.108.40.206"top
void CkAuthAzureStorageW_putXMsVersion(HCkAuthAzureStorageW cHandle, const wchar_t *newVal);
const wchar_t *CkAuthAzureStorageW_xMsVersion(HCkAuthAzureStorageW cHandle);
If set, automatically adds the "x-ms-version" HTTP request header to Azure Storage requests. The default value is "2014-02-14".top
Saves the last-error information (the contents of LastErrorXml) to an XML formatted file.
Returns TRUE for success, FALSE for failure.top