[
https://issues.apache.org/jira/browse/IGNITE-16809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615273#comment-17615273
]
Jerome Isaac Haltom commented on IGNITE-16809:
----------------------------------------------
It is generally accepted that signaling a cancellation may not take effect
immediately, only that the state of the application be left consistent. That
the user be capable of cancelling the network portions of the call seems fine
to me. That can be a significant amount of time in an application shutdown
situation, especially if the shutdown is unorderly, and the remote Ignite
service goes down first, leaving the client in a state of waiting for a timeout.
> .NET CancellationToken on Async methods
> ---------------------------------------
>
> Key: IGNITE-16809
> URL: https://issues.apache.org/jira/browse/IGNITE-16809
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Affects Versions: 2.12
> Reporter: Jerome Isaac Haltom
> Priority: Minor
>
> 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)
