Possible Duplicate:
Why Java needs Serializable interface?
What are the negative consequences to serialize an object? There must be some place or Sun all serializable objects. The Serializable interface need not even exist.
Asked
Active
Viewed 134 times
0
Community
- 1
- 1
Ismael Dos Anjos
- 21
- 1
- 3
-
I think it was just coincidence – Ismael Dos Anjos Aug 16 '12 at 11:47
-
Chapter 11 of Joshua Bloch's Effective Java (2nd ed.) is a good read if you want to understand some of the pitfalls and attack vectors that exist for serialized objects. He describes some solid techniques to try and mitigate said problems. – Duncan Jones Aug 16 '12 at 11:54
-
I liked the proposal, when I have free time I'll try to remember – Ismael Dos Anjos Aug 16 '12 at 11:57
2 Answers
1
Some objects can not be safely serialized without extra code, for example if they have an open socket. If you serialize and deserialize the object, the socket will not magically have opened again.
Sjoerd
- 74,049
- 16
- 131
- 175
1
Serialization provides a second means (after the constructors) to instantiate objects. If you have created a singleton class, this can result in more than one object existing when you don't expect it.
matt freake
- 4,877
- 4
- 27
- 56