You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2021/03/24 06:59:00 UTC
[jira] [Created] (IGNITE-14382) Network module API structuring
Sergey Chugunov created IGNITE-14382:
----------------------------------------
Summary: Network module API structuring
Key: IGNITE-14382
URL: https://issues.apache.org/jira/browse/IGNITE-14382
Project: Ignite
Issue Type: Sub-task
Components: networking
Reporter: Sergey Chugunov
Fix For: 3.0.0-alpha2
First version of the network module introduced a NetworkCluster interface providing access to all functionality of the module: sending and receiving messages in p2p fashion, topology API (current set of online nodes, node join and left events) and some lifecycle-related methods.
Further development has shown that it makes sense to gather these pieces of functionality under separate interfaces that should be accessible from NetworkCluster or similar single entry point.
Suggestions for naming of these interfaces: *Topology* and *Messaging*. Keeping lifecycle callbacks and methods under the same interface seems natural at the moment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)