The Config type exposes the following members.
The maximum waiting time to either acquire an idle connection from the pool when connection pool is full or create a new connection when pool is not full.
The idle timeout on pooled connections. A connection that has been idled in connection pool for longer than the given timeout is stale and will be closed once it is seen. Use InfiniteInterval to disable idle time checking.
The connection timeout when establishing a connection with a server.
The default read buffer size which the driver allocates for its internal buffers.
The default write buffer size which the driver allocates for its internal buffers.
The use of encryption for all the connections created by the IDriver.
The default fetch size. Since Bolt v4 (Neo4j 4.0+), the query running result (records) are pulled from server in batches. This fetch size defines how many records to pull in each batch. Use Infinite to disable batching and always pull all records in one batch instead.
The connections to support ipv6 addresses.
The ILogger instance to be used to receive all logs produced by this driver.
The maximum connection lifetime on pooled connections. A connection that has been created for longer than the given time will be closed once it is seen. Use InfiniteInterval to disable connection lifetime checking.
The max connection pool size.
The max idle connection pool size. If the value of this is not internal set, then it will default to be the same as MaxConnectionPoolSize
The size when internal read buffers reach, will be released for garbage collection. If reading large records (nodes, relationships or paths) and experiencing too much garbage collection consider increasing this size to a reasonable amount depending on your data.
The maximum transaction retry timeout.
The size when internal write buffers reach, will be released for garbage collection. If writing large values and experiencing too much garbage collection consider increasing this size to a reasonable amount depending on your data.
Gets or internal sets a custom server address resolver used by the routing driver to resolve the initial address used to create the driver. Such resolution happens: 1) during the very first rediscovery when driver is created. 2) when all the known routers from the current routing table have failed and driver needs to fallback to the initial address.
The socket keep alive option.
Specifies which TrustManager implementation should be used while establishing trust via TLS.
Used to get and set the User Agent string. If not used the default will be "neo4j-dotnet/x.y" where x is the major version and y is the minor version.