[
https://issues.apache.org/jira/browse/IGNITE-15944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461479#comment-17461479
]
Roman Puchkovskiy commented on IGNITE-15944:
--------------------------------------------
One more thing. It is not planned to persist class descriptors and their IDs,
so it will be possible to deserialize a serialized object only in the same
session during which it was deserialized. As long as the session is closed,
everything that was not serialized becomes unparseable blobs.
So this feature will be useable for exchange via network (and it is intended to
be used for this), but it won't be useable for long-term storage, for example.
The spec right now does not highlight this property. It would be great to
explicitly mention it in the spec.
> [Networking] User object serialization
> --------------------------------------
>
> Key: IGNITE-15944
> URL: https://issues.apache.org/jira/browse/IGNITE-15944
> Project: Ignite
> Issue Type: Epic
> Reporter: Semyon Danilov
> Priority: Major
> Labels: iep-67, ignite-3
> Fix For: 3.0.0-alpha4
>
>
> Arbitrary objects serialization must be provided by Apache Ignite. Unlike
> {{NetworkMessage}} descendants, user objects are not known to the system in
> advance, and serialization layout must be resolved at runtime.
> For more information look at the
> https://github.com/gridgain/gridgain-9-ce/blob/iep-67/modules/network/README.md
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
