[
https://issues.apache.org/jira/browse/TINKERPOP-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601849#comment-16601849
]
ASF GitHub Bot commented on TINKERPOP-1774:
-------------------------------------------
Github user jorgebay commented on the issue:
https://github.com/apache/tinkerpop/pull/903
Its one send at a time, that means that we have to send it one at a time
but not necessary awaiting to receive after each send.
```c#
// Send in a loop until the queue is exhausted
while (writeQueue.TryDequeue(out var item))
{
await ws.SendAsync(item);
}
```
```c#
// Always have an outstanding receiveasync call
// We should not await on the ReceiveAsync()
ws.ReceiveAsync().ContinueWith(
item =>
{
ParseItem(item);
ReceiveNext();
}
, ExecuteSynchronously);
```
> 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)
