[
https://issues.apache.org/jira/browse/IGNITE-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-16928:
----------------------------------------
Fix Version/s: 3.2
(was: 3.1)
> Thin 3.0: Implement sessions for Java client
> --------------------------------------------
>
> Key: IGNITE-16928
> URL: https://issues.apache.org/jira/browse/IGNITE-16928
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
> Affects Versions: 3.0.0-alpha4
> Reporter: Igor Sapego
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: iep-90, ignite-3
> Fix For: 3.2
>
>
> Let's implement local sessions for Java client.
> Sessions AKA logical connections are described in
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-90+Client+Lifecycle.
> What needs to be implemented is:
> 1. On handshake server should generate a Connection ID and return it in
> HandshakeRsp;
> 2. Client should save a Connection ID and associate it with a node it
> connected to;
> 3. If disconnected, server should not at once clean up connection associated
> data but start timer instead. Timeout should be configurable by server config;
> 4. If client manages to send a proper ConnectionRestoreReq during timeout,
> the session is restored;
> 5. All results of all operations that were complete while physical connection
> is broken is stored within session data and sent back to client if connection
> is restored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
