[
https://issues.apache.org/jira/browse/TINKERPOP-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600722#comment-17600722
]
Florian Hockmann commented on TINKERPOP-2794:
---------------------------------------------
We basically already have a ticket for this: TINKERPOP-2210.
That was originally mainly focused on .NET, but since we first need support for
cancellation on the server, we decided that it should be implement there first.
I'm wondering however whether we should maybe just add support for cancellation
already in .NET so that the client can at least release its resources and shut
down, although the server might still evaluate traversals sent by that client,
where the results will be ignored. We should probably just document clearly
that the {{CancellationToken}} will not stop the server from evaluating a
traversal that was already sent.
So, my suggestion here would be that we don't treat this as a duplicate of
TINKERPOP-2210 which is now mainly about supporting proper cancellation
server-side and instead simply at {{CancellationTokens}} in .NET to close open
connections.
> Allow cancellation of Gremlin.Net async methods
> -----------------------------------------------
>
> Key: TINKERPOP-2794
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2794
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Reporter: Bill Poole
> Priority: Major
>
> Gremlin.Net async methods such as Promise do not accept a CancellationToken
> parameter and cannot therefore be cancelled. Applications often need to be
> closed quickly/responsively when a user quits or an application server
> component is shut down/rebooted - e.g., during cluster auto
> scaling/rebalancing.
> All async methods should accept a CancellationToken parameter (which can be
> given a default value of 'default').
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
