Classes that will be used with hazelcast data structures like IMap, IQueue etc should either inherit from one of the following classes : Portable , IdentifiedDataSerializable or it should be custom serializable.
More...
#include <Portable.h>
Classes that will be used with hazelcast data structures like IMap, IQueue etc should either inherit from one of the following classes : Portable , IdentifiedDataSerializable or it should be custom serializable.
For custom serializable see Serializer
Portable serialization that have the following advantages:
-
Support multiversion of the same object type. See SerializationConfig::setPortableVersion(int)}
-
Fetching individual fields without having to rely on reflection.
-
Querying and indexing support without de-serialization and/or reflection.
Note that: factoryId and classId is to the same class in find server side, hence they should be consistent with each other.
- See also
- IdentifiedDataSerializable
| virtual int hazelcast::client::serialization::Portable::getClassId |
( |
| ) |
const |
|
pure virtual |
| virtual int hazelcast::client::serialization::Portable::getFactoryId |
( |
| ) |
const |
|
pure virtual |
| virtual void hazelcast::client::serialization::Portable::readPortable |
( |
PortableReader & |
reader | ) |
|
|
pure virtual |
Defines how this class will be read.
- Parameters
-
| virtual void hazelcast::client::serialization::Portable::writePortable |
( |
PortableWriter & |
writer | ) |
const |
|
pure virtual |
Defines how this class will be written.
- Parameters
-
The documentation for this class was generated from the following file:
- hazelcast/include/hazelcast/client/serialization/Portable.h
Inheritance diagram for hazelcast::client::serialization::Portable:
1.8.11
