You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Jorge Bay (JIRA)" <ji...@apache.org> on 2018/10/17 13:39:00 UTC
[jira] [Created] (TINKERPOP-2070) gremlin-javascript: Introduce
Connection representation
Jorge Bay created TINKERPOP-2070:
------------------------------------
Summary: gremlin-javascript: Introduce Connection representation
Key: TINKERPOP-2070
URL: https://issues.apache.org/jira/browse/TINKERPOP-2070
Project: TinkerPop
Issue Type: Improvement
Components: javascript
Reporter: Jorge Bay
Assignee: Jorge Bay
Currently on gremlin-javascript, {{DriverRemoteConnection}} represents a single connection to the server and a {{RemoteConnection}} implementation.
Like Python and .NET, we need to make the {{DriverRemoteConnection}} use the {{Client}} instead of a websocket.
The dependency tree between classes should be like the following
{code:java}
DriverRemoteConnection
|_ Client
|_ Connection
{code}
This doesn't represent a breaking change, its more of an implementation issue. As {{DriverRemoteConnection}} is part of the public API the current implementation is a limitation.
This blocks or at least forces awful workarounds for improvements like TINKERPOP-2064.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)