<br><br><div class="gmail_quote">On Wed, May 25, 2011 at 5:31 PM, Yanni Chiu <span dir="ltr"><<a href="mailto:yanni@rogers.com">yanni@rogers.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 25/05/11 11:22 AM, Mariano Martinez Peck wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- globals behaviors (classes and traits) are managed (by default) in<br>
kind of "light" serialization. Where we only serialize the global name<br>
which means that the class has to be present in Smalltalk globals in the<br>
image that you want to materialize.<br>
<br>
You can change the default behavior and be able to completely serialize<br>
a class/trait. But this is much more complicated and it is still work on<br>
process (ClassBuilder is not your best friend).<br>
</blockquote>
<br></div>
Okay. I think all that is needed is a "safe mode" option when *de-serializing*, which would discard any non-light classes or global objects that appear in the stream.<br>
<br>
<br>
</blockquote></div><br>Sorry Yanni, I didn't follow. Could you please explain a bit more? what do you want to serialize? do you want to be able to choose some classes as light and some as non-light? where do you want to materialize ? in the same image or in another one ? When you said discard....what would you do with the instances of those non-light classes for example? you don't materialize them? and what happens to the objects that were pointing to them ? why would be the scenario useful for ? security ?<br>
<br clear="all">Thanks<br><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>