<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Serialization - Page 28 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=serialization&amp;p=27">1.Previous</a><br />
<a accesskey="3" href="page.php?w=serialization&amp;p=29">3.Next</a>
</p>
<p>a  object is tied to the state of the current <a href="page.php?w=JVM">JVM</a>. There is no context in which a deserialized <code>Thread</code> object would maintain useful semantics.<br />Secondly, the serialized state of an object forms part of its class' compatibility contract. Maintaining compatibility between versions of serializable classes requires additional effort and consideration. Therefore, making a class serializable needs to be a deliberate design decision and not a default condition.<br />Lastly, serialization allows access to</p><p>
<a accesskey="1" href="page.php?w=serialization&amp;p=27">1.Previous</a><br />
<a accesskey="3" href="page.php?w=serialization&amp;p=29">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
