@@ -92,10 +92,7 @@ in the same group representing the original data unit.
9292#### API:
9393
9494``` java
95- public class Chunk implements Serializable {
96-
97- private static final long serialVersionUID = 42L ;
98-
95+ public class Chunk {
9996 /**
10097 * The group ID of the original data blob. All chunks in the same group share the same group ID.
10198 */
@@ -123,10 +120,12 @@ public class Chunk implements Serializable {
123120#### Usage example:
124121
125122Chunk4J aims to handle most details of the ` Chunk ` behind the scenes of the ` Chopper ` and ` Stitcher ` API. For the API
126- client, it suffices to know that ` Chunk ` is a simple POJO data holder; serializable, it carries the data bytes
127- travelling from the ` Chopper ` to the ` Stitcher ` . To transport Chunks over the network, the API client simply needs to
128- pack the Chunk into a transport-specific message on the Chopper's end, and unpack the message back to a Chunk on the
129- Stitcher's end, using the POJO marshal-unmarshal technique applicable to the transport.
123+ client, it suffices to know that ` Chunk ` is a simple POJO data holder, carrying a portion of the original data bytes
124+ from the ` Chopper ` to the ` Stitcher ` . To transport Chunks over the network, the API client simply needs to pack the
125+ Chunk into a transport-specific message on the Chopper's end, and unpack the message back to a Chunk on the Stitcher's
126+ end, using the marshaling(serialize)-unmarshalling(deserialize) technique applicable to that transport for a POJO. Note
127+ that ` Chunk ` does not implement ` java.io.Serializable ` , with the expectation that the external data transport, rather
128+ than the JVM, will take care of the serialization/deserialization.
130129
131130### The Stitcher
132131
0 commit comments