[
https://issues.apache.org/jira/browse/TINKERPOP-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566605#comment-16566605
]
ASF GitHub Bot commented on TINKERPOP-1774:
-------------------------------------------
Github user spmallette commented on a diff in the pull request:
https://github.com/apache/tinkerpop/pull/903#discussion_r207180470
--- Diff: docs/src/upgrade/release-3.4.x.asciidoc ---
@@ -177,6 +177,17 @@ when dealing with that event. To make this easier, the
event now raises with a `
link:https://issues.apache.org/jira/browse/TINKERPOP-1831[TINKERPOP-1831]
+==== Gremlin.Net: Configurable Max and Min ConnectionPool Sizes
--- End diff --
Also, while this is a nice explanation of the this feature, perhaps it's
time to add a "Configuration" section to the reference documentation itself? If
no one else agrees, that's fine - just a thought I had given this new feature.
No new users are going to find this nice explanation here in the upgrade docs i
don't think.
> 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)
