CkStream C++ Reference Documentation

CkStream

Current Version: 9.5.0.73

Provides a generic class for streaming from a source to a sink. Streams can be connected together where the sink of one feeds to the source of another.

Note: This class was added in Chilkat v9.5.0.56. Initially it will seem somewhat useless, but over time, streaming functionality will be added to existing Chilkat classes and will be prevalent in new Chilkat classes.

Object Creation

// Local variable on the stack
CkStream obj;

// Dynamically allocate/delete
CkStream *pObj = new CkStream();
// ...
delete pObj;

Properties

AbortCurrent
bool get_AbortCurrent(void);
void put_AbortCurrent(bool newVal);
Introduced in version 9.5.0.58

When set to true, causes the currently running method to abort. Methods that always finish quickly (i.e.have no length file operations or network communications) are not affected. If no method is running, then this property is automatically reset to false when the next method is called. When the abort occurs, this property is reset to false. Both synchronous and asynchronous method calls can be aborted. (A synchronous method call could be aborted by setting this property from a separate thread.)

top
CanRead
bool get_CanRead(void);
Introduced in version 9.5.0.56

true if the stream supports reading. Otherwise false.

Note: A stream that supports reading, which has already reached the end-of-stream, will still have a CanRead value of true. This property indicates the stream's inherent ability, and not whether or not the stream can be read at a particular moment in time.

top
CanWrite
bool get_CanWrite(void);
Introduced in version 9.5.0.56

true if the stream supports writing. Otherwise false.

Note: A stream that supports writing, which has already been closed for write, will still have a CanWrite value of true. This property indicates the stream's inherent ability, and not whether or not the stream can be written at a particular moment in time.

top
DataAvailable
bool get_DataAvailable(void);
Introduced in version 9.5.0.56

true if it is known for sure that data is ready and waiting to be read. false if it is not known for sure (it may be that data is immediately available, but reading the stream with a ReadTimeoutMs of 0, which is to poll the stream, is the way to find out).

top
DebugLogFilePath
void get_DebugLogFilePath(CkString &str);
const char *debugLogFilePath(void);
void put_DebugLogFilePath(const char *ansiOrUtf8Str);

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:

  1. a timeout related property was set to 0 to explicitly indicate that an infinite timeout is desired,
  2. the hang is actually a hang within an event callback (i.e. it is a hang within the application code), or
  3. there is an internal problem (bug) in the Chilkat code that causes the hang.

top
DefaultChunkSize
int get_DefaultChunkSize(void);
void put_DefaultChunkSize(int newVal);
Introduced in version 9.5.0.56

The default internal chunk size for reading or writing. The default value is 65536. If this property is set to 0, it will cause the default chunk size (65536) to be used. Note: The chunk size can have significant performance impact. If performance is an issue, be sure to experiment with different chunk sizes.

top
EndOfStream
bool get_EndOfStream(void);
Introduced in version 9.5.0.56

true if the end-of-stream has already been reached. When the stream has already ended, all calls to Read* methods will return false with the ReadFailReason set to 3 (already at end-of-stream).

top
IsWriteClosed
bool get_IsWriteClosed(void);
Introduced in version 9.5.0.56

true if the stream is closed for writing. Once closed, no more data may be written to the stream.

top
LastErrorHtml
void get_LastErrorHtml(CkString &str);
const char *lastErrorHtml(void);

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
LastErrorText
void get_LastErrorText(CkString &str);
const char *lastErrorText(void);

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
LastErrorXml
void get_LastErrorXml(CkString &str);
const char *lastErrorXml(void);

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
LastMethodSuccess
bool get_LastMethodSuccess(void);
void put_LastMethodSuccess(bool newVal);
Introduced in version 9.5.0.52

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
Length
__int64 get_Length(void);
void put_Length(__int64 newVal);
Introduced in version 9.5.0.56

The length (in bytes) of the stream's source. If unknown, then this property will have a value of -1. This property may be set by the application if it knows in advance the length of the stream.

top
Length32
int get_Length32(void);
void put_Length32(int newVal);
Introduced in version 9.5.0.58

The length (in bytes) of the stream's source. If unknown, then this property will have a value of -1. This property may be set by the application if it knows in advance the length of the stream.

Setting this property also sets the Length property (which is a 64-bit integer).

top
NumReceived
__int64 get_NumReceived(void);
Introduced in version 9.5.0.56

The number of bytes received by the stream.

top
NumSent
__int64 get_NumSent(void);
Introduced in version 9.5.0.56

The number of bytes sent by the stream.

top
ReadFailReason
int get_ReadFailReason(void);
Introduced in version 9.5.0.56

This property is automatically set when a Read* method is called. It indicates the reason for failure. Possible values are:

  1. No failure (success)
  2. Timeout, or no data is immediately available for a polling read.
  3. Aborted by an application callback.
  4. Already at end-of-stream.
  5. Fatal stream error.
  6. Out-of-memory error (this is very unlikely).

top
ReadTimeoutMs
int get_ReadTimeoutMs(void);
void put_ReadTimeoutMs(int newVal);
Introduced in version 9.5.0.56

The maximum number of seconds to wait while reading. The default value is 30 seconds (i.e. 30000ms). A value of 0 indicates a poll. (A polling read is to return with a timeout if no data is immediately available.)

Important: For most Chilkat timeout related properties, a value of 0 indicates an infinite timeout. For this property, a value of 0 indicates a poll. If setting a timeout related property (or method argument) to zero, be sure to understand if 0 means "wait forever" or "poll".

The timeout value is not a total timeout. It is the maximum time to wait while no additional data is forthcoming.

top
SinkFile
void get_SinkFile(CkString &str);
const char *sinkFile(void);
void put_SinkFile(const char *ansiOrUtf8Str);
Introduced in version 9.5.0.56

Sets the sink to the path of a file. The file does not need to exist at the time of setting this property. The sink file will be automatically opened on demand, when the stream is first written.

Note: This property takes priority over other potential sinks. Make sure this property is set to an empty string if the stream's sink is to be something else.

More Information and Examples
top
SourceFile
void get_SourceFile(CkString &str);
const char *sourceFile(void);
void put_SourceFile(const char *ansiOrUtf8Str);
Introduced in version 9.5.0.56

Sets the source to the path of a file. The file does not need to exist at the time of setting this property. The source file will be automatically opened on demand, when the stream is first read.

Note: This property takes priority over other potential sources. Make sure this property is set to an empty string if the stream's source is to be something else.

More Information and Examples
top
SourceFilePart
int get_SourceFilePart(void);
void put_SourceFilePart(int newVal);
Introduced in version 9.5.0.59

If the source is a file, then this property can be used to stream one part of the file. The SourceFilePartSize property defines the size (in bytes) of each part. The SourceFilePart and SourceFilePartSize have default values of 0, which means the entire SourceFile is streamed.

This property is a 0-based index. For example, if the SourceFilePartSize is 1000, then part 0 is for bytes 0 to 999, part 1 is for bytes 1000 to 1999, etc.

More Information and Examples
top
SourceFilePartSize
int get_SourceFilePartSize(void);
void put_SourceFilePartSize(int newVal);
Introduced in version 9.5.0.59

If the source is a file, then this property, in conjunction with the SourceFilePart property, can be used to stream a single part of the file. This property defines the size (in bytes) of each part. The SourceFilePart and SourceFilePartSize have default values of 0, which means that by default, the entire SourceFile is streamed.

More Information and Examples
top
StringBom
bool get_StringBom(void);
void put_StringBom(bool newVal);
Introduced in version 9.5.0.56

If true, then include the BOM when creating a string source via SetSourceString where the charset is utf-8, utf-16, etc. (The term "BOM" stands for Byte Order Mark, also known as the preamble.) Also, if true, then include the BOM when writing a string via the WriteString method. The default value of this property is false.

top
StringCharset
void get_StringCharset(CkString &str);
const char *stringCharset(void);
void put_StringCharset(const char *ansiOrUtf8Str);
Introduced in version 9.5.0.56

Indicates the expected character encoding, such as utf-8, windows-1256, utf-16, etc. for methods that read text such as: ReadString, ReadToCRLF, ReadUntilMatch. Also controls the character encoding when writing strings with the WriteString method. The supported charsets are indicated at the link below.

The default value is "utf-8".

More Information and Examples
top
Utf8
bool get_Utf8(void);
void put_Utf8(bool newVal);

When set to true, all "const char *" arguments are interpreted as utf-8 strings. If set to false (the default), then "const char *" arguments are interpreted as ANSI strings. Also, when set to true, and Chilkat method returning a "const char *" is returning the utf-8 representation. If set to false, all "const char *" return values are ANSI strings.

top
VerboseLogging
bool get_VerboseLogging(void);
void put_VerboseLogging(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
Version
void get_Version(CkString &str);
const char *version(void);

Version of the component/library, such as "9.5.0.63"

top
WriteFailReason
int get_WriteFailReason(void);
Introduced in version 9.5.0.56

This property is automatically set when a Write* method is called. It indicates the reason for failure. Possible values are:

  1. No failure (success)
  2. Timeout, or unable to immediately write when the WriteTimeoutMs is 0.
  3. Aborted by an application callback.
  4. The stream has already ended.
  5. Fatal stream error.
  6. Out-of-memory error (this is very unlikely).

top
WriteTimeoutMs
int get_WriteTimeoutMs(void);
void put_WriteTimeoutMs(int newVal);
Introduced in version 9.5.0.56

The maximum number of seconds to wait while writing. The default value is 30 seconds (i.e. 30000ms). A value of 0 indicates to return immediately if it is not possible to write to the sink immediately.

top

Methods

ReadBd
bool ReadBd(CkBinData &binData);
Introduced in version 9.5.0.67

Read as much data as is immediately available on the stream. If no data is immediately available, it waits up to ReadTimeoutMs milliseconds for data to arrive. The incoming data is appended to binData.

Returns true for success, false for failure.

More Information and Examples
top
ReadBdAsync (1)
CkTask *ReadBdAsync(CkBinData &binData);
Introduced in version 9.5.0.67

Creates an asynchronous task to call the ReadBd method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

More Information and Examples
top
ReadBytes
bool ReadBytes(CkByteData &outBytes);
Introduced in version 9.5.0.56

Read as much data as is immediately available on the stream. If no data is immediately available, it waits up to ReadTimeoutMs milliseconds for data to arrive.

Returns true for success, false for failure.

top
ReadBytesAsync (1)
CkTask *ReadBytesAsync(void);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the ReadBytes method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
ReadBytesENC
bool ReadBytesENC(const char *encoding, CkString &outStr);
const char *readBytesENC(const char *encoding);
Introduced in version 9.5.0.56

The same as ReadBytes, except returns the received bytes in encoded string form. The encoding argument indicates the encoding, which can be "base64", "hex", or any of the multitude of encodings indicated in the link below.

Returns true for success, false for failure.

More Information and Examples
top
ReadBytesENCAsync (1)
CkTask *ReadBytesENCAsync(const char *encoding);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the ReadBytesENC method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
ReadNBytes
bool ReadNBytes(int numBytes, CkByteData &outBytes);
Introduced in version 9.5.0.56

Reads exactly numBytes bytes from the stream. If no data is immediately available, it waits up to ReadTimeoutMs milliseconds for data to arrive.

Returns true for success, false for failure.

top
ReadNBytesAsync (1)
CkTask *ReadNBytesAsync(int numBytes);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the ReadNBytes method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
ReadNBytesENC
bool ReadNBytesENC(int numBytes, const char *encoding, CkString &outStr);
const char *readNBytesENC(int numBytes, const char *encoding);
Introduced in version 9.5.0.56

The same as ReadNBytes, except returns the received bytes in encoded string form. The encoding argument indicates the encoding, which can be "base64", "hex", or any of the multitude of encodings indicated in the link below.

Returns true for success, false for failure.

More Information and Examples
top
ReadNBytesENCAsync (1)
CkTask *ReadNBytesENCAsync(int numBytes, const char *encoding);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the ReadNBytesENC method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
ReadSb
bool ReadSb(CkStringBuilder &sb);
Introduced in version 9.5.0.67

Read as much data as is immediately available on the stream. If no data is immediately available, it waits up to ReadTimeoutMs milliseconds for data to arrive. The data is appended to sb. The incoming bytes are interpreted according to the StringCharset property. For example, if utf-8 bytes are expected, then StringCharset should be set to "utf-8" prior to calling ReadSb.

Returns true for success, false for failure.

top
ReadSbAsync (1)
CkTask *ReadSbAsync(CkStringBuilder &sb);
Introduced in version 9.5.0.67

Creates an asynchronous task to call the ReadSb method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

More Information and Examples
top
ReadString
bool ReadString(CkString &outStr);
const char *readString(void);
Introduced in version 9.5.0.56

Read as much data as is immediately available on the stream. If no data is immediately available, it waits up to ReadTimeoutMs milliseconds for data to arrive. The data is returned as a string. The incoming bytes are interpreted according to the StringCharset property. For example, if utf-8 bytes are expected, then StringCharset should be set to "utf-8" prior to calling ReadString.

Returns true for success, false for failure.

top
ReadStringAsync (1)
CkTask *ReadStringAsync(void);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the ReadString method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
ReadToCRLF
bool ReadToCRLF(CkString &outStr);
const char *readToCRLF(void);
Introduced in version 9.5.0.56

Reads the stream until a CRLF is received. If no data is immediately available, it waits up to ReadTimeoutMs milliseconds for data to arrive. The data is returned as a string. The incoming bytes are interpreted according to the StringCharset property. For example, if utf-8 bytes are expected, then StringCharset should be set to "utf-8" prior to calling ReadString.

Note: If the end-of-stream is reached prior to receiving the CRLF, then the remaining data is returned, and the ReadFailReason property will be set to 3 (to indicate end-of-file). This is the only case where as string would be returned that does not end with CRLF.

Returns true for success, false for failure.

top
ReadToCRLFAsync (1)
CkTask *ReadToCRLFAsync(void);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the ReadToCRLF method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
ReadUntilMatch
bool ReadUntilMatch(const char *matchStr, CkString &outStr);
const char *readUntilMatch(const char *matchStr);
Introduced in version 9.5.0.56

Reads the stream until the string indicated by matchStr is received. If no data is immediately available, it waits up to ReadTimeoutMs milliseconds for data to arrive. The data is returned as a string. The incoming bytes are interpreted according to the StringCharset property. For example, if utf-8 bytes are expected, then StringCharset should be set to "utf-8" prior to calling ReadString.

Note: If the end-of-stream is reached prior to receiving the match string, then the remaining data is returned, and the ReadFailReason property will be set to 3 (to indicate end-of-file). This is the only case where as string would be returned that does not end with the desired match string.

Returns true for success, false for failure.

top
ReadUntilMatchAsync (1)
CkTask *ReadUntilMatchAsync(const char *matchStr);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the ReadUntilMatch method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
Reset
void Reset(void);
Introduced in version 9.5.0.56

Resets the stream. If a source or sink is open, then it is closed. Properties such as EndOfStream and IsWriteClose are reset to default values.

top
RunStream
bool RunStream(void);
Introduced in version 9.5.0.56

Runs the stream to completion. This method should only be called when the source of the string has been set by any of the following methods: SetSourceBytes, SetSourceString, or SetSourceStream, or when the SourceFile property has been set (giving the stream a file source).

This method will read the stream source and forward to the sink until the end-of-stream is reached, and all data has been written to the sink.

Returns true for success, false for failure.

More Information and Examples
top
RunStreamAsync (1)
CkTask *RunStreamAsync(void);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the RunStream method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
SaveLastError
bool SaveLastError(const char *path);

Saves the last-error information (the contents of LastErrorXml) to an XML formatted file.

Returns true for success, false for failure.

top
SetSinkStream
bool SetSinkStream(CkStream &strm);
Introduced in version 9.5.0.56

Sets the stream's sink to strm. Any data written to this stream's sink will become available to strm on its source.

Returns true for success, false for failure.

top
SetSourceBytes
bool SetSourceBytes(CkByteData &sourceData);
Introduced in version 9.5.0.56

Sets the stream's source to the contents of sourceData.

Returns true for success, false for failure.

top
SetSourceStream
bool SetSourceStream(CkStream &strm);
Introduced in version 9.5.0.56

Sets the stream's source to be the sink of strm. Any data written to strm's sink will become available on this stream's source.

Returns true for success, false for failure.

More Information and Examples
top
SetSourceString
bool SetSourceString(const char *srcStr, const char *charset);
Introduced in version 9.5.0.56

Sets the stream's source to the contents of srcStr. The charset indicates the character encoding to be used for the byte representation of the srcStr.

Returns true for success, false for failure.

top
WriteBd
bool WriteBd(CkBinData &binData);
Introduced in version 9.5.0.67

Writes the contents of binData to the stream.

Returns true for success, false for failure.

top
WriteBdAsync (1)
CkTask *WriteBdAsync(CkBinData &binData);
Introduced in version 9.5.0.67

Creates an asynchronous task to call the WriteBd method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
WriteByte
bool WriteByte(int byteVal);
Introduced in version 9.5.0.56

Writes a single byte to the stream. The byteVal must have a value from 0 to 255.

Returns true for success, false for failure.

top
WriteByteAsync (1)
CkTask *WriteByteAsync(int byteVal);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the WriteByte method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
WriteBytes
bool WriteBytes(CkByteData &byteData);
Introduced in version 9.5.0.56

Writes binary bytes to a stream.

Returns true for success, false for failure.

top
WriteBytesAsync (1)
CkTask *WriteBytesAsync(CkByteData &byteData);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the WriteBytes method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
WriteBytesENC
bool WriteBytesENC(const char *byteData, const char *encoding);
Introduced in version 9.5.0.56

Writes binary bytes to a stream. The byte data is passed in encoded string form, where the encoding can be "base64", "hex", or any of the supported binary encodings listed at the link below.

Returns true for success, false for failure.

More Information and Examples
top
WriteBytesENCAsync (1)
CkTask *WriteBytesENCAsync(const char *byteData, const char *encoding);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the WriteBytesENC method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
WriteClose
bool WriteClose(void);
Introduced in version 9.5.0.56

Indicates that no more data will be written to the stream.

Returns true for success, false for failure.

top
WriteSb
bool WriteSb(CkStringBuilder &sb);
Introduced in version 9.5.0.67

Writes the contents of sb to the stream. The actual bytes written are the byte representation of the string as indicated by the StringCharset property. For example, to write utf-8 bytes, first set StringCharset equal to "utf-8" and then call WriteSb.

Returns true for success, false for failure.

top
WriteSbAsync (1)
CkTask *WriteSbAsync(CkStringBuilder &sb);
Introduced in version 9.5.0.67

Creates an asynchronous task to call the WriteSb method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top
WriteString
bool WriteString(const char *str);
Introduced in version 9.5.0.56

Writes a string to a stream. The actual bytes written are the byte representation of the string as indicated by the StringCharset property. For example, to write utf-8 bytes, first set StringCharset equal to "utf-8" and then call WriteString.

Returns true for success, false for failure.

top
WriteStringAsync (1)
CkTask *WriteStringAsync(const char *str);
Introduced in version 9.5.0.56

Creates an asynchronous task to call the WriteString method with the arguments provided. (Async methods are available starting in Chilkat v9.5.0.52.)

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Note: The application is responsible for deleting (via the C++ delete operator) the object returned by this method.

Returns NULL on failure

top

Events

To implement an event callback, your application would define and implement a class that inherits from CkBaseProgress. Your application can implement methods to override some or all of the default/empty method implementations of the CkBaseProgress base class.

For example:

  CkStream stream;

  MyStreamProgress callbackObj;

  stream.put_EventCallbackObject(&callbackObj);

MyStreamProgress example:

#include "CkBaseProgress.h"

class MyStreamProgress : public CkBaseProgress {

  public:
    MyStreamProgress();
    virtual ~MyStreamProgress();

    void AbortCheck(bool  *abort);

    void BinaryData(const void *data, unsigned int length);

    void PercentDone(int pctDone, bool  *abort);

    void ProgressInfo(const char *name, const char *value);

    void TaskCompleted(CkTask &task);

    void TextData(const char *data);

};
AbortCheck
void AbortCheck(bool *abort);

Provides the opportunity for a method call to be aborted. The AbortCheck event is fired periodically based on the value of the HeartbeatMs property. If HeartbeatMs is 0, then no AbortCheck events will fire. As an example, to fire 5 AbortCheck events per second, set the HeartbeatMs property equal to 200.

top
PercentDone
void PercentDone(int pctDone, bool *abort);

Provides the percentage completed for any method that involves network communications or time-consuming processing (assuming it is a method where a percentage completion can be measured). This event is only fired when it is possible to know a percentage completion, and when it makes sense to express the operation as a percentage completed. The pctDone argument will have a value from 1 to 100. For operations (Chilkat method calls) that complete very quickly, the number of PercentDone callbacks will vary, but the final callback should have a value of 100. For long running operations, no more than one callback per percentage point will occur (for example: 1, 2, 3, ... 98, 99, 100).

The PercentDone callback counts as an AbortCheck event. For method calls that complete quickly such that PercentDone events fire, it may be that AbortCheck events don't fire because the opportunity to abort is already provided in the PercentDone callback. For time consuming operations, where the amount of time between PercentDone callbacks are long, AbortCheck callbacks may be used to allow for the operation to be aborted in a more responsive manner.

The abort output argument provides a means for aborting the operation. Setting it to true will cause the method to abort and return a failed status (or whatever return value indicates failure).

top
ProgressInfo
void ProgressInfo(const char *name, const char *value);

A general name/value event that provides information about what is happening during a method call. To find out what information is available, write code to handle this event and log the name/value pairs. Most are self-explanatory.

top
TaskCompleted
void TaskCompleted(CkTask &task);

Called in the background thread when an asynchronous task completes.

top