tinkerpop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From spmalle...@apache.org
Subject [6/9] tinkerpop git commit: TINKERPOP-1726 Minor fix to ascidoc format
Date Fri, 23 Feb 2018 12:42:02 GMT
TINKERPOP-1726 Minor fix to ascidoc format


Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/a082e63e
Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/a082e63e
Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/a082e63e

Branch: refs/heads/master
Commit: a082e63e6a999411fceb618c66d49e214ed52ff7
Parents: da48b74
Author: Stephen Mallette <spmva@genoprime.com>
Authored: Tue Feb 20 10:56:29 2018 -0500
Committer: Stephen Mallette <spmva@genoprime.com>
Committed: Tue Feb 20 10:56:29 2018 -0500

----------------------------------------------------------------------
 docs/src/reference/gremlin-applications.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/a082e63e/docs/src/reference/gremlin-applications.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/reference/gremlin-applications.asciidoc b/docs/src/reference/gremlin-applications.asciidoc
index 5443ee2..380ff4e 100644
--- a/docs/src/reference/gremlin-applications.asciidoc
+++ b/docs/src/reference/gremlin-applications.asciidoc
@@ -1074,7 +1074,7 @@ The following table describes the various configuration options that
Gremlin Ser
 |gremlinPool |The number of "Gremlin" threads available to execute actual scripts in a `ScriptEngine`.
This pool represents the workers available to handle blocking operations in Gremlin Server.
When set to `0`, Gremlin Server will use the value provided by `Runtime.availableProcessors()`.
|0
 |host |The name of the host to bind the server to. |localhost
 |idleConnectionTimeout |Time in milliseconds that the server will allow a channel to not
receive requests from a client before it automatically closes. If enabled, the value provided
should typically exceed the amount of time given to `keepAliveInterval`. Note that while this
value is to be provided as milliseconds it will resolve to second precision. Set this value
to `0` to disable this feature. |0
-|keepAliveInterval |Time in milliseconds that the server will allow a channel to not send
responses to a client before it sends a "ping" to see if it is still present. If it is present,
the client should respond with a "pong" which will thus reset the `#idleConnectionTimeout`
and keep the channel open. If enabled, this number should be smaller than the value provided
to the `idleConnectionTimeout`. Note that while this value is to be provided as milliseconds
it will resolve to second precision. Set this value to `0` to disable this feature. |0
+|keepAliveInterval |Time in milliseconds that the server will allow a channel to not send
responses to a client before it sends a "ping" to see if it is still present. If it is present,
the client should respond with a "pong" which will thus reset the `idleConnectionTimeout`
and keep the channel open. If enabled, this number should be smaller than the value provided
to the `idleConnectionTimeout`. Note that while this value is to be provided as milliseconds
it will resolve to second precision. Set this value to `0` to disable this feature. |0
 |maxAccumulationBufferComponents |Maximum number of request components that can be aggregated
for a message. |1024
 |maxChunkSize |The maximum length of the content or each chunk.  If the content length exceeds
this value, the transfer encoding of the decoded request will be converted to 'chunked' and
the content will be split into multiple `HttpContent` objects.  If the transfer encoding of
the HTTP request is 'chunked' already, each chunk will be split into smaller chunks if the
length of the chunk exceeds this value. |8192
 |maxContentLength |The maximum length of the aggregated content for a message.  Works in
concert with `maxChunkSize` where chunked requests are accumulated back into a single message.
 A request exceeding this size will return a `413 - Request Entity Too Large` status code.
 A response exceeding this size will raise an internal exception. |65536


Mime
View raw message