[
https://issues.apache.org/jira/browse/TINKERPOP-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598888#comment-16598888
]
ASF GitHub Bot commented on TINKERPOP-1774:
-------------------------------------------
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/903
> We should allow sending multiple requests without waiting for a response
and support unordered responses (based on the request id)
Wouldn't that mean that the server sends responses as soon as they are
ready on the connection that was used to send the request? And couldn't that
result in multiple responses being sent over the same connection in parallel?
In that case I'm afraid that it wouldn't work with the `ClientWebSocket` we're
currently relying on due to this restriction:
> Exactly one send and one receive is supported on each ClientWebSocket
object in parallel.
[Source](https://docs.microsoft.com/dotnet/api/system.net.websockets.clientwebsocket.sendasync?view=netcore-2.1#remarks)
Or did I misunderstand this somehow?
> 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)
