Eliminating the need to subclass seems pretty convenient to me.

I’ve found two libs covering this approach:

https://github.com/threerings/java-signals

https://github.com/paulmoore/Java-Signals

Nice article, btw!

My point with the article is that while they exist, those needs are hard to come by in the Flash platform. I guess my issue is that sometimes I see people with Java or C experience working in ActionScript and being surprised it doesn’t have threads – because they expect to *need* to use threads to do anything. But that’s often not the case, just because of the way the language is actually designed, and people with experience in other platforms should be aware of that.

But think about a situation where you are an animation running in the screen and you call some service in background, if the result of this service is a json or something you need to parsing, your animation will be blocked to running this task. It’s a bad thing.

In my opinion, it’s the most common situation where threads could be help.

A good practice to avoid this, is to wait until the end of expressive animations to do non visual tasks like read data, but sometimes it’s sounds like a “workaround”, because you delay to display the most important information to user.

Even though the flashplayer’s performance is enough to do any parse, serialization, deserialization, anyway… threads are welcome to help in this point.

in Java you access methods..
most of this ‘behaviour’ is part of the JavaBean spec. you can also take a look into the java.beans package, there are reason for the convention/spec to still be used till this date.

cheers,
D.

How would this work for application from flash
I have searched but can not find the way
thanks