|
- Since serialization does not offer any transaction control mechanism per se, it is not suitable for use within applications needing concurrent access without making use of additional APIs.
-
It should ideally not be used with large sized objects as it offers significant overhead.
- Large objects also significantly increase the memory requirements of your application since the object input/output streams cache live references to all objects written to or read from the stream until the stream is closed or reset.
-
The serialization interface does not offer fine grained control over object access although you can somewhat circumvent this issue by implementing the complex Externalizable interface, instead.
|