[jira] [Commented] (TINKERPOP-2379) Ensure that all driver URL paths are configurable

["Stephen Mallette (Jira)" <ji...@apache.org>]

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

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

Might also be worth considering configurations from a file. Java allows that but other drivers do not.

> Ensure that all driver URL paths are configurable
> -------------------------------------------------
>
>                 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.



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