[
https://issues.apache.org/jira/browse/IGNITE-14295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-14295:
-------------------------------------
Description:
Network module should introduce a public Message interface to handle messages
to send and receive.
This interface should provide at least information about message type (and
possible version) to enable effective serialization/deserialization and ability
to subscribe for a messages of certain type.
API clarifications:
# Message should not be responsible for reading itself from and writing to a
byte buffer. Some kind of builder/converted has to be introduced.
# We need a factory for instantiating Message objects or builders/converters
for these objects by message type.
# We need a requirement for components workflow so components can register
their message types in network component and make sure there are no conflicts
between them.
was:
Network module should introduce a public Message interface to handle messages
to send and receive.
This interface should provide at least information about message type (and
possible version) to enable effective serialization/deserialization and ability
to subscribe for a messages of certain type.
> Message interface to be introduced
> ----------------------------------
>
> Key: IGNITE-14295
> URL: https://issues.apache.org/jira/browse/IGNITE-14295
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Sergey Chugunov
> Priority: Major
> Fix For: 3.0.0-alpha2
>
>
> Network module should introduce a public Message interface to handle messages
> to send and receive.
> This interface should provide at least information about message type (and
> possible version) to enable effective serialization/deserialization and
> ability to subscribe for a messages of certain type.
> API clarifications:
> # Message should not be responsible for reading itself from and writing to a
> byte buffer. Some kind of builder/converted has to be introduced.
> # We need a factory for instantiating Message objects or builders/converters
> for these objects by message type.
> # We need a requirement for components workflow so components can register
> their message types in network component and make sure there are no conflicts
> between them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
