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 2021/07/01 19:16:00 UTC

[jira] [Commented] (TINKERPOP-2379) Consistent defaults and initialization APIs for drivers

    [ https://issues.apache.org/jira/browse/TINKERPOP-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373004#comment-17373004 ] 

Stephen Mallette commented on TINKERPOP-2379:
---------------------------------------------

Implemented part of this as CTR: https://github.com/apache/tinkerpop/commit/7dc8def58e0cf366792379cc4eaeb74a0a1c02fe 

> Consistent defaults and initialization APIs for drivers
> -------------------------------------------------------
>
>                 Key: TINKERPOP-2379
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2379
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.4.6
>            Reporter: Stephen Mallette
>            Priority: Minor
>
> Some drivers allow the connection URL to be directly set which means that it is wholly configurable. For example, Javascript allows:
> {code}
> const g = traversal().withRemote(new DriverRemoteConnection('ws://localhost:8182/gremlin'));
> {code}
> Python allows something similar, but Java and .NET do not. I don't recall a reason for that inconsistency and there are times when it seems that such options would be helpful.
> In addition, some drivers will take a file for configuration and some will not. Furthermore, defaults for various settings are different from one driver to the next. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)