[ 
https://issues.apache.org/jira/browse/IGNITE-14817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Polovtcev updated IGNITE-14817:
-----------------------------------------
    Description: 
The network component is currently only able to serialize objects that either 
extend the {{NetworkMesssage}} interface or that belong to a predefined set of 
types, like strings, primitives and different collections. This is 
inconvenient, because messages might contain other objects as their properties, 
which might not extend {{NetworkMessage}}.

It is proposed to update the current serialization infrastructure to use the 
new {{@Transferrable}} annotation to generate serialization classes and to 
decouple it from the {{NetworkMessage}} interface in order to use it for 
arbitrary objects that satisfy the same contract as the current serializable 
message do.

  was:
The network component is currently only able to serialize objects that either 
extend the {{NetworkMesssage}} interface or that belong to a predefined set of 
types, like strings, primitives and different collections. This is 
inconvenient, because messages might contain other objects as their properties, 
which might not extend {{NetworkMessage}}.

It is proposed to update the current serialization infrastructure to use the 
new {{@Transferrable}} annotation to generate serialization classes and to 
decouple it from the {{NetworkMessage }}interface in order to use it for 
arbitrary objects that satisfy the same contract as the current serializable 
message do.


> Custom serializable types
> -------------------------
>
>                 Key: IGNITE-14817
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14817
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: networking
>            Reporter: Aleksandr Polovtcev
>            Priority: Major
>
> The network component is currently only able to serialize objects that either 
> extend the {{NetworkMesssage}} interface or that belong to a predefined set 
> of types, like strings, primitives and different collections. This is 
> inconvenient, because messages might contain other objects as their 
> properties, which might not extend {{NetworkMessage}}.
> It is proposed to update the current serialization infrastructure to use the 
> new {{@Transferrable}} annotation to generate serialization classes and to 
> decouple it from the {{NetworkMessage}} interface in order to use it for 
> arbitrary objects that satisfy the same contract as the current serializable 
> message do.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to