Comments on: Class Deserialization: OpenAMF & Flashcom

By: Plato

Plato — Thu, 06 Nov 2008 05:17:19 +0000

agrees, but with this it can not be helped, it is in their blood

By: Jason Nussbaum

Jason Nussbaum — Wed, 01 Feb 2006 16:57:42 +0000

I’m only running into this issue now, so hadn’t seen this thread before, but…
Couldn’t you use the same ‘workaround’ that UIComponent uses for handling clip parameters? That would solve it (and, actually, I think it’s exactly the same problem).

I’ll have to give it a try and post my results…

By: JesterXL

JesterXL — Tue, 19 Apr 2005 21:33:24 +0000

It seems your constructor fires after all of your properties have their values set; I wasn’t seeing this in my Flashcom examples last night, but Brian Lesser from the Flashcom list sent me a working example. If it does work, I’ll see if there isn’t a way to set the privates during the constructor, thus having my getters work once the class is ready to be accessed. Stay tuned….

By: Patrick Mineault

Patrick Mineault — Tue, 19 Apr 2005 21:29:50 +0000

I’ve seen this also in some of the AMFPHP example files. I think a decent workaround is creating an init method for that object, and running it immediately after you receive the object in the result event. This init method can transpose the variables to getters/setters.

By: JesterXL

JesterXL — Tue, 19 Apr 2005 21:05:37 +0000

Vanilla, like:

var o = {};
o.prop = ‘value’;

That’s an AS1 vanilla object. You could also do:

var o:Object = {};

or:

var o:Object = new Object();

Either way, if you trace it out:

trace(o.__proto__ == Object.prototype); // true

What I think Flash does when it’s deserializing your class from the AMF packets is taking this instance, and going:

o.__proto__ = YourClass.prototype;

Where YourClass is what you registered too up top in your code:

Object.registerClass(‘YourClass’, YourClass);

If Java sends a ‘YourClass’ class, then Flash then knows to map it to a YourClass, an ActionScript class.