Ken Hu created TINKERPOP-3217:
---------------------------------
Summary: Add mechanism to close session without closing connection
on server
Key: TINKERPOP-3217
URL: https://issues.apache.org/jira/browse/TINKERPOP-3217
Project: TinkerPop
Issue Type: Improvement
Components: server
Affects Versions: 3.7.5, 3.8.0
Reporter: Ken Hu
Currently, the Gremlin Server expects a closing of the underlying connection to
signal that the corresponding Session tied to the connection should be closed.
This is part of the [SessionOpProcessor
reference|https://tinkerpop.apache.org/docs/current/dev/provider/#_session_opprocessor].
An option should be added to the server so that alternative would be that the
Session closes automatically if a successful commit or rollback occurs. This
would only affect the Bytecode portion of the SessionOpProcessor that makes the
Session act like a Transaction. This would allow connection re-use of
connections for sessions and enable better performance for use cases that
require large number of transactions to occur.
This needs to be an option to prevent breaking changes in the server in 3.7.x
and 3.8.x. In 4.x and later, this should probably be the default option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
