Re: GCancellable hints

> GCancellable's only purpose is as a token that ensures function calls can be
> cancelled over thread or operating system boundaries. In an async program, the
> same cancellable is often used for multiple calls at the same time. Operation
> is one-way: The caller cancels the function call.

These are similar to my thoughts too -- and I appreciate the feedback.

> I should also note that GIO functions put transaction information into
> separate parameters passed to the function call - g_file_copy() for example
> has the progress_callback parameters. They do not attach this information to
> the cancellable.

Right, I mostly agree with what you've said, so we'll leave it to Alex
to decide if GCancellable should be a one-way action, or something
designed to push state back up to the caller.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]