Package net.openhft.chronicle.hash.serialization

The package contains interfaces for serializing objects and values between Java heap and Bytes or BytesStore.

See: Description

Interface Summary

Interface	Description
BytesReader<T>	External version on ReadBytesMarshallable.
BytesWriter<T>	External version of WriteBytesMarshallable.
DataAccess<T>
SizedReader<T>	Deserializer of objects from bytes, mirroring the SizedWriter, i.
SizedWriter<T>	Serializer (object to bytes writer) which 1) 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>>	Stateful implementations of marshaller interfaces (SizedReader, SizedWriter, BytesReader, BytesWriter, DataAccess), configured for ChronicleMap or ChronicleSet in builder, should implement the StatefulCopyable interface.

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

The package contains interfaces for serializing objects and values between Java heap and Bytes or BytesStore.

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.