You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2022/06/15 06:52:00 UTC
[jira] [Comment Edited] (IGNITE-16928) Thin 3.0: Implement sessions for Java client
[ https://issues.apache.org/jira/browse/IGNITE-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554410#comment-17554410 ]
Pavel Tupitsyn edited comment on IGNITE-16928 at 6/15/22 6:51 AM:
------------------------------------------------------------------
Stopping the progress due to extra uncovered complexity and priority shift.
https://lists.apache.org/thread/38fxj1f2yg3kxcm0k84ln61l3yg1ybbr
was (Author: ptupitsyn):
Stopping the progress due to extra uncovered complexity and priority shift.
> 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: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> 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.7#820007)