You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/09/10 15:17:45 UTC
[jira] [Closed] (TINKERPOP3-726) Limit Visibility To
ServerGremlinExecutor
[ https://issues.apache.org/jira/browse/TINKERPOP3-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP3-726.
---------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 3.1.0-incubating)
Looking at this again - not sure what my concern was. Going to just leave {{ServerGremlinExecutor}} alone.
> Limit Visibility To ServerGremlinExecutor
> -----------------------------------------
>
> Key: TINKERPOP3-726
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-726
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.1-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
>
> Calls to {{GremlnServer.start()}} return a {{CompletableFuture<ServerGremlinExecutor>}} which perhaps exposes a bit more of the Gremlin Server internals than it should. Consider whether protecting certain bits is important or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)