Package net.openhft.chronicle.hash.serialization

Contains interfaces for serializing objects between Java heap and Bytes or BytesStore, used by Chronicle Map to store objects off-heap, and read them back from off-heap memory to on-heap objects.

See: Description

Interface Summary

Interface	Description
BytesReader<T>	Deserializer of objects from bytes, pairing BytesWriter, without accepting additional information about serialized objects.
BytesWriter<T>	Serializer of objects to bytes, pairing BytesReader.
DataAccess<T>	Strategy of accessing flat byte contents of objects, using a reusable Data object, cached inside the DataAccess instance.
SizedReader<T>	Deserializer of objects from bytes, pairing SizedWriter, i.
SizedWriter<T>	Serializer of objects to bytes, pairing SizedReader, which knows the length of serialized form of any object before actual serialization 2) doesn't include that length in the serialized form itself, assuming it will be passed by the ChronicleHash into SizedReader.read(net.openhft.chronicle.bytes.Bytes, long, T) deserialization method.
SizeMarshaller	Strategy of storing numbers in bytes stores (usually sizes of the subsequent chunks in the same bytes store).
StatefulCopyable<T extends StatefulCopyable<T>>	Cloneable-like interface used by Chronicle Map to populate stateful serializer implementations for each isolated site (thread + Chronicle Map instance + objects domain).

Class Summary

Class	Description
ListMarshaller<T>	Marshaller of List<T>.
MapMarshaller<K,V>	Marshaller of Map<K, V>.
SetMarshaller<T>	Marshaller of Set<T>.

Package net.openhft.chronicle.hash.serialization Description

Contains interfaces for serializing objects between Java heap and Bytes or BytesStore, used by Chronicle Map to store objects off-heap, and read them back from off-heap memory to on-heap objects.

Read Custom serializers section in the Chronicle Map tutorial for more information.

Reading methods in the interfaces in this package could use StreamingDataInput as the "input" parameter type and StreamingDataOutput as the "output" parameter type, but always use just Bytes and BytesStore, though this is "unsafe" because somebody could make a mistake and write into bytes supposed to be read-only or read some garbage bytes. This is done because of the poor support of StreamingDataInput/StreamingDataOutput in Chronicle Bytes and other projects. Byteable, BytesMarshallable, Chronicle Wire and others support only BytesStore or Bytes, but not read/write separated interfaces.