[
https://issues.apache.org/jira/browse/IGNITE-16809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615284#comment-17615284
]
Jerome Isaac Haltom commented on IGNITE-16809:
----------------------------------------------
Last part of that paragraph:
>or find a convenient place that you can stop halfway through but in a valid
>condition, before then throwing OperationCanceledException. In other words,
>the caller must be able to recover to a known consistent state after
>cancelling your work, or realize that cancellation was not responded to and
>that the caller then must decide whether to accept the work, or revert its
>successful completion on its own.
A "consistent state" isn't meant to convey that the entire operation should be
atomic. That's a job for something larger, like transactions.
If you were to interpret the paragraph how you want, all idempotent HTTP
operations should be uncancellable.
> .NET: CancellationToken on Async methods
> ----------------------------------------
>
> Key: IGNITE-16809
> URL: https://issues.apache.org/jira/browse/IGNITE-16809
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Affects Versions: 2.12
> Reporter: Jerome Isaac Haltom
> Assignee: Pavel Tupitsyn
> Priority: Minor
> Labels: .NET
>
> The .NET ThinClient API has numerous async methods, but none seem to support
> cancellation. I suspect they could and probably should. Each should accept a
> CancellationToken parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
