Task

Chilkat.Task obj = new Chilkat.Task();

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

true if the task status is "canceled", "aborted", or "completed". A task can only reach the "canceled" status if it was activated via the Run method, made it onto the internal thread pool thread's queue, was waiting for a pool thread to become available, and was then canceled prior to the task actually starting.

top

The number of milliseconds between each AbortCheck event callback. The AbortCheck callback allows an application to abort the Wait method. If HeartbeatMs is 0 (the default), no AbortCheck event callbacks will fire. Note: An asynchronous task running in a background thread (in one of the thread pool threads) does not fire events. The task's event callbacks pertain only to the Wait method.

top

true if the task status is "empty" or "loaded". When a task is inert, it has been loaded but is not scheduled to run yet.

top

Determines if the in-memory progress info event log is kept. The default value is false and therefore no log is kept. To enable progress info logging, set this property equal to true (prior to running the task).

top

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

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

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

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

true if the task status is "queued" or "running". When a task is live, it is either already running, or is on the thread pool thread's queue waiting for a thread to become available.

top

Indicates the percent completion while the task is running. The percent completed information is only available in cases where it is possible to know the percentage completed. For some methods, it is never possible to know, such as for methods that establish TCP or TLS connections. For other methods it is always possible to know -- such as for sending email (because the size of the email to be sent is already known). For some methods, it may or may not be possible to know the percent completed. For example, if an HTTP response is "chunked", there is no Content-Length header and therefore the receiver has no knowledge of the size of the forthcoming response body.

Also, the value of the PercentDoneScale property of the asynchronous method's object determines the scale, such as 0 to 100, or 0 to 1000, etc.

top

What would normally be a ProgressInfo event callback (assuming Chilkat supports event callbacks for this language) is instead saved to an in-memory progress log that can be examined and pruned while the task is still running. This property returns the number of progress log entries that are currently available. (Note: the progress log is only kept if the KeepProgressLog property is turned on. By default, the KeepProgressLog is turned off.)

top

The LastErrorText for the task's asynchronous method.

top

Indicates the data type of the task's result. This property is only available after the task has completed. Possible values are "bool", "int", "string", "bytes", "object", and "void". For example, if the result data type is "bool", then call GetResultBool to get the boolean result of the underlying asynchronous method.

For example, if the synchronous version of the method returned a boolean, then in the asynchronous version of the method, the boolean return value is made available via the GetResultBool method.

top

The current status of the task. Possible values are:

• "empty" -- The method call and arguments are not yet loaded into the task object. This can only happen if a task was explicitly created instead of being returned by a method ending in "Async".
• "loaded" -- The method call and arguments are loaded into the task object.
• "queued" -- The task is in the thread pool's queue of tasks awaiting to be run.
• "running" -- The task is currently running.
• "canceled" -- The task was canceled before it entered the "running" state.
• "aborted" -- The task was canceled while it was in the running state.
• "completed" -- The task completed. The success or failure depends on the semantics of the method call and the value of the result.

top

The current status of the task as an integer value. Possible values are:

• 1 -- The method call and arguments are not yet loaded into the task object. This can only happen if a task was explicitly created instead of being returned by a method ending in "Async".
• 2 -- The method call and arguments are loaded into the task object.
• 3 -- The task is in the thread pool's queue of tasks awaiting to be run.
• 4 -- The task is currently running.
• 5 -- The task was canceled before it entered the "running" state.
• 6 -- The task was canceled while it was in the running state.
• 7 -- The task completed. The success or failure depends on the semantics of the method call and the value of the result.

top

A unique integer ID assigned to this task. The purpose of this property is to help an application identify the task if a TaskCompleted event callback is used.

top

This is the value of the LastMethodSuccess property of the underlying task object. This property is only valid for those methods where the LastMethodSuccess property would be valid had the method been called synchronously.

Important: This property is only meaningful for cases where the underlying method call has a non-boolean return value (such as for methods that return strings, other Chilkat objects, or integers). If the underlying method call returns a boolean, then call the GetResultBool() method instead to get the boolean return value.

top

An application may use this property to attach some user-specific information with the task, which may be useful if a TaskCompleted event callback is used.

top

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 of the component/library, such as "9.5.0.94"

top

Marks an asynchronous task for cancellation. The expected behavior depends on the current status of the task as described here:

• "loaded" - If the task has been loaded but has not yet been queued to run in the thread pool, then there is nothing to do. (There is nothing to cancel because the task's Run method has not yet been called.) The task will remain in the "loaded" state.
• "queued" - The task is marked for cancellation, is dequeued, and will not run. The task's status changes immediately to "canceled".
• "running" - The already-running task is marked for cancellation. The task's status will eventually change to "aborted" when the asynchronous method returns. At that point in time, the ResultErrorText property will contain the "LastErrorText" of the method call. In the case where a task is marked for cancellation just at the time it's completing, the task status may instead change to "completed".
• "canceled", "aborted", "completed" - In these cases the task has already finished, and there will be no change in status.

Cancel returns true if the task was in the "queued" or "running" state when it was marked for cancellation. Cancel returns false if the task was in any other state.

Important: Calling the Cancel method marks a task for cancellation. It sets a flag in memory that the running task will soon notice and then abort. It is important to realize that your application is likely calling Cancel from the main UI thread, whereas the asynchronous task is running in a background thread. If the task was in the "running" state when Cancel was called, it will still be in the "running" state when Cancel returns. It will take a short amount of time until the task actually aborts. This is because operating systems schedule threads in time slices, and the thread needs one or more time slices to notice the cancellation flag and abort. After calling Cancel, your application might wish to call the Wait method to wait until the task has actually aborted, or it could periodically check the task's status and then react once the status changes to "aborted".

top

Removes all entries from the progress info log.

top

Returns the binary bytes result of the task. The bytes are copied to the caller.

Returns an empty byte array on failure

top

Returns the boolean result of the task.

top

Returns the binary bytes result of the task. The bytes are transferred to the caller, not copied. Call CopyResultBytes instead to copy the result bytes.

Returns an empty byte array on failure

top

Returns the integer result of the task.

top

Returns the string result of the task.

Returns null on failure

top

Returns the name of the Nth progress info event logged. The 1st entry is at index 0.

Returns null on failure

top

Returns the value of the Nth progress info event logged. The 1st entry is at index 0.

Returns null on failure

top

Removes the Nth progress info log entry.

top

Queues the task to run on the internal Chilkat thread pool.

Returns true for success, false for failure.

top

Runs the task synchronously. Then this method returns after the task has been run.

Returns true for success, false for failure.

top

Convenience method to force the calling thread to sleep for a number of milliseconds. (This does not cause the task's background thread to sleep.)

top

Waits for the task to complete. Returns when task has completed, or after maxWaitMs milliseconds have elapsed. (A maxWaitMs value of 0 is to wait indefinitely.) Returns (false) if the task has not yet been started by calling the Run method, or if the maxWaitMs expired. If the task completed, was already completed, was canceled or aborted, then this method returns true.

Returns true for success, false for failure.

top

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.

Chilkat .NET Event Implementation

Args are passed using Chilkat.AbortCheckEventArgs

Event callback implementation:

private void task_OnAbortCheck(object sender, Chilkat.AbortCheckEventArgs args)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
task.OnAbortCheck += task_OnAbortCheck;

Chilkat Mono/.NET Core Event Implementation

Event callback implementation:

public void handleAbortCheck(out bool abort)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
// ...
Chilkat.Task.AbortCheck abortCheck = new Chilkat.Task.AbortCheck(handleAbortCheck);
task.setAbortCheckCb(abortCheck);

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).

Chilkat .NET Event Implementation

Args are passed using Chilkat.PercentDoneEventArgs

Event callback implementation:

private void task_OnPercentDone(object sender, Chilkat.PercentDoneEventArgs args)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
task.OnPercentDone += task_OnPercentDone;

Chilkat Mono/.NET Core Event Implementation

Event callback implementation:

public void handlePercentDone(int pctDone, out bool abort)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
// ...
Chilkat.Task.PercentDone percentDone = new Chilkat.Task.PercentDone(handlePercentDone);
task.setPercentDoneCb(percentDone);

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.

Chilkat .NET Event Implementation

Args are passed using Chilkat.ProgressInfoEventArgs

Event callback implementation:

private void task_OnProgressInfo(object sender, Chilkat.ProgressInfoEventArgs args)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
task.OnProgressInfo += task_OnProgressInfo;

Chilkat Mono/.NET Core Event Implementation

Event callback implementation:

public void handleProgressInfo(string name, string value)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
// ...
Chilkat.Task.ProgressInfo progressInfo = new Chilkat.Task.ProgressInfo(handleProgressInfo);
task.setProgressInfoCb(progressInfo);

Called in the background thread when an asynchronous task completes.

Chilkat .NET Event Implementation

Args are passed using Chilkat.TaskCompletedEventArgs

Event callback implementation:

private void task_OnTaskCompleted(object sender, Chilkat.TaskCompletedEventArgs args)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
task.OnTaskCompleted += task_OnTaskCompleted;

Chilkat Mono/.NET Core Event Implementation

Event callback implementation:

public void handleTaskIdCompleted(int taskId)
	{
	    // application code goes here.
	}

To add an event handler:

Chilkat.Task task = new Chilkat.Task();
// ...
Chilkat.Task.TaskIdCompleted taskIdCompleted = new Chilkat.Task.TaskIdCompleted(handleTaskIdCompleted);
task.setTaskIdCompletedCb(taskIdCompleted);