You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Jerome Isaac Haltom (Jira)" <ji...@apache.org> on 2022/10/10 19:44:00 UTC

[jira] [Comment Edited] (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=17615285#comment-17615285 ] 

Jerome Isaac Haltom edited comment on IGNITE-16809 at 10/10/22 7:43 PM:
------------------------------------------------------------------------

For instance, it's well accepted that you should be able to cancel a PUT request when using HTTP client, but that you should except the operation to be idempotent: that your client might try the operation again, without knowing whether the previous operation completed.

This matches exactly the putCache etc methods on Ignite.


was (Author: JIRAUSER287703):
For instance, it's well accepted that you should be able to cancel a PUT request when using HTTP client, but that you should except the operation to be idempotent: that your client might try the operation again, without knowing whether the previous operation completed.

This matches exactly the putCache etc methods on Ignote.

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