Description
IgniteProxy exists to handle serialization of injected IIgnite fields in user classes.
As a result, we write a type id and a null flag in place of injected fields.
Instead we should just skip injected fields altogether.
There are two cases:
- Binarizable. In this case we can use a special no-op serializer or add a check to BinaryWriter.
- Serializable. Override ISerializable in Ignite and don't write anything.
Attachments
Issue Links
- is blocked by
-
IGNITE-2703 .NET: Dynamically registered classes must use binary serialization if possible
- Resolved
- Is contained by
-
IGNITE-4547 Apache Ignite 2.0 quick and needed tasks
- Resolved
- links to