[
https://issues.apache.org/jira/browse/TINKERPOP-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834623#comment-16834623
]
stephen mallette commented on TINKERPOP-2210:
---------------------------------------------
There is no server cancellation (though i guess with sessions you could call
"close" on the session and that would work) so the traversal would be left to
timeout on the server.
> Support cancellation of traversals in Gremlin.Net
> -------------------------------------------------
>
> Key: TINKERPOP-2210
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2210
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.4.1
> Reporter: Florian Hockmann
> Priority: Minor
>
> It should be possible to cancel a traversal in Gremlin.Net, for example when
> an application shuts down. This involves the following steps:
> * Cancel the send operation.
> * Cancel the task the user is awaiting on by cancelling the underlying
> {{TaskCompletionSource}}. This means that any received data for this
> traversal needs to be ignored afterwards.
> * Cancel the operation on the server if possible.
> I'm not sure if / how we can cancel the operation on the server. If it's not
> easy to do that right now, then we should just start by cancelling everything
> only client-side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
