Current implementation of sessions and the session pool doesn't include the control of the session state.
And we often have next problems:
Usage of session after closing
Parallel usage of one session
Deleting session by client error or canceling
We can resolve these problem by adding the control of current session state - idle, active, executing, canceled and etc. And every action on the session can check this state and returns an error if client uses session in wrong way
Current implementation of sessions and the session pool doesn't include the control of the session state. And we often have next problems:
We can resolve these problem by adding the control of current session state - idle, active, executing, canceled and etc. And every action on the session can check this state and returns an error if client uses session in wrong way