You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Shishkov (Jira)" <ji...@apache.org> on 2026/04/20 07:19:00 UTC
[jira] [Updated] (IGNITE-27627) Refactor custom message serialization
[ 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 {{DiscoveryCustomMessage}} into {{TcpDiscoveryCustomEventMessage}}.
Moreover, {{TcpDiscoveryCustomEventMessage#msgByte}} and {{#serMsg}} are used for marshalling / unmarshalling. They also should be removed (it could be possible, when all custom messages will migrate to the new framework).
We can at least, remove {{prepareMarshal}} / {{finishUnmarshall}} from {{TcpDiscoveryCustomEventMessage}} or remove {{TcpDiscoveryCustomEventMessage}} at all and serialize {{DiscoveryCustomMessage}} directly via {{TcpDiscoveryIoSession}}.
Also:
# {{SecurityAwareCustomMessageWrapper}} should be refactored.
# Support of {{Serializable}} messages can be removed from {{TcpDiscoveryIoSession}}, etc.
was:
To transfer custom message, we need wrap {{DiscoveryCustomMessage}} into {{TcpDiscoveryCustomEventMessage}}.
Moreover, {{TcpDiscoveryCustomEventMessage#msgByte}} and {{#serMsg}} are used for marshalling / unmarshalling. They also should be removed (it could be possible, when all custom messages will migrate to the new framework).
We can at least, remove {{prepareMarshal}} / {{finishUnmarshall}} from {{TcpDiscoveryCustomEventMessage}} or remove {{TcpDiscoveryCustomEventMessage}} at all and serialize {{DiscoveryCustomMessage}} directly via {{TcpDiscoveryIoSession}}.
Also, {{SecurityAwareCustomMessageWrapper}} should be refactored.
> 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
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> To transfer custom message, we need wrap {{DiscoveryCustomMessage}} into {{TcpDiscoveryCustomEventMessage}}.
> Moreover, {{TcpDiscoveryCustomEventMessage#msgByte}} and {{#serMsg}} are used for marshalling / unmarshalling. They also should be removed (it could be possible, when all custom messages will migrate to the new framework).
> We can at least, remove {{prepareMarshal}} / {{finishUnmarshall}} from {{TcpDiscoveryCustomEventMessage}} or remove {{TcpDiscoveryCustomEventMessage}} at all and serialize {{DiscoveryCustomMessage}} directly via {{TcpDiscoveryIoSession}}.
> Also:
> # {{SecurityAwareCustomMessageWrapper}} should be refactored.
> # Support of {{Serializable}} messages can be removed from {{TcpDiscoveryIoSession}}, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)