Steve
John de Michele wrote:Deepak:
You don't have to implement the Serializable interface, if you don't ever intend to serialize your class. In fact, for many classes, using Serializable doesn't make sense. Serialization has nothing to do with sharing class files, though.
John.
deepak mishra Singh wrote:i think i failed to present my question properly. i would reframe it.
the first "hello world" program i wrote, never implemented the serializable interface. still, i could save/ persist the class file on my harddisk,or across the network (which is what is serialization supposed to do). how was that possible ? what difference would it have made if it implemented the serializable interface ?
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
fred rosenberger wrote: As long as that second JVM knows about the class (i.e. has the class file), it too can restore the STATE of the object.