TinkerPop uses WebSocket as the primary transport. WebSocket was designed
to ride over and/or be compatible with HTTP. Thus, either by design or by
accident, TinkerPop inherits all the features of HTTP. This would include
the ability to support HTTP proxies (load balancers), name-based virtual
h
[
https://issues.apache.org/jira/browse/TINKERPOP-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968054#comment-16968054
]
ASF GitHub Bot commented on TINKERPOP-2289:
---
robertdale commented on pull r
See:
1. [User
list](https://groups.google.com/d/msg/gremlin-users/A9rr9jLh5AY/DLguF9QmAQAJ)
2. [Dev list]()
[ Full content available at: https://github.com/apache/tinkerpop/pull/1213 ]
This message was relayed via gitbox.apache.org for dev@tinkerpop.apache.org