[
https://issues.apache.org/jira/browse/TINKERPOP-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598528#comment-16598528
]
ASF GitHub Bot commented on TINKERPOP-1774:
-------------------------------------------
Github user jorgebay commented on the issue:
https://github.com/apache/tinkerpop/pull/903
Also, I'm not sure I understand how this will come into place with
TINKERPOP-1775.
Currently a connection is being used to one send and receive one
request/response pair at a time. We should allow sending multiple requests
without waiting for a response and support unordered responses (based on the
request id). You can look at the gremlin-javascript connection for example:
- When the request is sent, a [callback handler is
registered](https://github.com/apache/tinkerpop/blob/3.3.3/gremlin-javascript/src/main/javascript/gremlin-javascript/lib/driver/driver-remote-connection.js#L106-L109)
- When the response is obtained, [the callback is obtained by request id
and
invoked](https://github.com/apache/tinkerpop/blob/3.3.3/gremlin-javascript/src/main/javascript/gremlin-javascript/lib/driver/driver-remote-connection.js#L146).
We can use the pool to balance the requests between connections. If we want
to throttle requests, we should introduce a new setting like "max inflight per
connection".
> Gremlin .NET: Support min and max sizes in Connection pool
> ----------------------------------------------------------
>
> Key: TINKERPOP-1774
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1774
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.2.7
> Reporter: Jorge Bay
> Assignee: Florian Hockmann
> Priority: Minor
>
> Similar to the java connection pool, we should limit the maximum amount of
> connections and start with a minimum number.
> It would also a good opportunity to remove the synchronous acquisitions of
> {{lock}} in the pool implementation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
