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 2023/04/03 06:44:00 UTC

[jira] [Commented] (IGNITE-18820) .NET: Thin 3.0: Add cancellation to all async APIs

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

Pavel Tupitsyn commented on IGNITE-18820:
-----------------------------------------

We can't cancel a request with side effects once it has been sent (written to the socket). 

However, cancellation can still be useful:
* We can cancel while waiting on *sendLock*
* We can cancel ongoing retries

> .NET: Thin 3.0: Add cancellation to all async APIs
> --------------------------------------------------
>
>                 Key: IGNITE-18820
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18820
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> All async APIs should accept `CancellationToken` and propagate it down the stack.
> https://devblogs.microsoft.com/premier-developer/recommended-patterns-for-cancellationtoken/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)