[
https://issues.apache.org/jira/browse/IGNITE-27627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-27627:
-----------------------------------
Description:
To transfer custom message, we need wrap {{DiscoverySpiCustomMessage}} into
{{TcpDiscoveryCustomEventMessage}}, and in turn {{DiscoveryCustomMessage}} into
{{DiscoverySpiCustomMessage}}.
This logic seems to be redundant and should be refactored.
Moreover, {{TcpDiscoveryCustomEventMessage#msgByte}} for marshalling /
unmarshalling. They are also should be removed.
was:
If all custom messages moved to new framework it should be investigated whether
{{TcpDiscoveryCustomEventMessage}} can be removed at all.
Or, at least duplication of fields inside it should be eliminated.
> Refactor custom message serialization
> -------------------------------------
>
> Key: IGNITE-27627
> URL: https://issues.apache.org/jira/browse/IGNITE-27627
> Project: Ignite
> Issue Type: Task
> Reporter: Ilya Shishkov
> Assignee: Ilya Shishkov
> Priority: Major
> Labels: IEP-132, ise
>
> To transfer custom message, we need wrap {{DiscoverySpiCustomMessage}} into
> {{TcpDiscoveryCustomEventMessage}}, and in turn {{DiscoveryCustomMessage}}
> into {{DiscoverySpiCustomMessage}}.
> This logic seems to be redundant and should be refactored.
> Moreover, {{TcpDiscoveryCustomEventMessage#msgByte}} for marshalling /
> unmarshalling. They are also should be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
