Releases: JoniSt/NetSerializer
Releases · JoniSt/NetSerializer
NetSerializer v1.1 (added final field support)
Changes
- Final fields can now be serialized and deserialized.
Features
- Simple serialization of Java objects into a DataOutput
- Produces very little overhead over the actual raw data contained in a serialized object
- Serialization of primitive Java types, Strings, Lists, Sets, Maps and Class objects built-in and optimized
- Supports inheritance and composition of serializable types
- Supports custom readers/writers for specific classes to reduce overhead or speed up serialization even further
Limitations
- Does not allow cycles in the object graph to be serialized
- The serializer needs to know the serializable classes beforehand
- No versioning of serializable classes (assumes sender and receiver of serializable data have compatible versions of classes)
- No support for array types yet (use collections instead)
- Fields containing collections have to be declared as their interface types (i.e. "List<...>" instead of "ArrayList<...>", which is good practice anyway)
Initial release version
The initial, working version of the library.
Features
- Simple serialization of Java objects into a DataOutput
- Produces very little overhead over the actual raw data contained in a serialized object
- Serialization of primitive Java types, Strings, Lists, Sets, Maps and Class objects built-in and optimized
- Supports inheritance and composition of serializable types
- Supports custom readers/writers for specific classes to reduce overhead or speed up serialization even further
Limitations
- No support for final fields (added in v1.1)
- Does not allow cycles in the object graph to be serialized
- The serializer needs to know the serializable classes beforehand
- No versioning of serializable classes (assumes sender and receiver of serializable data have compatible versions of classes)
- No support for array types yet (use collections instead)
- Fields containing collections have to be declared as their interface types (i.e. "List<...>" instead of "ArrayList<...>", which is good practice anyway)