You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2022/10/10 19:38:00 UTC

[jira] [Commented] (IGNITE-16809) .NET: CancellationToken on Async methods

    [ https://issues.apache.org/jira/browse/IGNITE-16809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615281#comment-17615281 ] 

Pavel Tupitsyn commented on IGNITE-16809:
-----------------------------------------

On the other hand, this guide https://devblogs.microsoft.com/premier-developer/recommended-patterns-for-cancellationtoken/ says *"Don’t cancel if you’ve already incurred side-effects that your method isn’t prepared to revert"*, which is true for all Ignite APIs that modify data. So we can only cancel the network response processing part for APIs that do not modify data, like *cache.get*.

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