Comments on: Callback Strategies

By: Fast AS3 Signals with SignalsLite | unFocus Projects

Fast AS3 Signals with SignalsLite | unFocus Projects — Tue, 06 Dec 2011 01:18:29 +0000

[...] this in a class that would expose signals. This example is based on the performance test from Jackson Dunstan’s CallbackTest which I borrowed (I hope that’s [...]

By: devu

devu — Thu, 05 May 2011 19:19:54 +0000

Regarding to Flash and Mobile development
[...]If you are still concern about it, take a look here or try it by yourself.[...]

By: Paul

Paul — Mon, 25 Oct 2010 21:32:37 +0000

Thanks. I’ll check out the article.

Some context switching would be in keeping with the reason for using callbacks.

By: jackson

jackson — Mon, 25 Oct 2010 17:26:09 +0000

I don't think you're missing anything. The title of the article is "Callback Strategies", so it's all about the performance of various ways of implementing callbacks. One of those ways is via a Function-typed variable, like you say you use, but another is to use the Runnable/observer strategy as discussed in the previous article. The Runnable strategy allows you to use typed functions as you're calling a typed function of the Runnable object. This typed function is the callback. This huge speed boost gives rise to my TurboSignals library, which is a very fast way of implementing an events/signals system using the Runnable/observer strategy.

By: paul

paul — Mon, 25 Oct 2010 16:58:52 +0000

Not sure I follow the reason for comparing generic function calling and typed function calling in the same class, or context. I only use Function types when providing a callback to out of context functions. Am I missing something?

By: Things I learnt recently « Tahir Ahmed's thoughts

Things I learnt recently « Tahir Ahmed's thoughts — Tue, 09 Mar 2010 08:37:03 +0000

[...] Penner, I owe you for that one; you are the man. AS3Signals is simply fantastic. With different tests showing the speed of this event mechanism and a presentation and a video tutorial showing how easy [...]

By: Weekly Shared Items – 23. February, 2010 | TOXIN LABS - weblog of a german design student from wuerzburg

Tue, 23 Feb 2010 06:04:47 +0000

[...] Callback Strategies [...]

By: jackson

jackson — Tue, 16 Feb 2010 18:33:02 +0000

I updated to your latest source (Git from last night, 2/15/2010) and my re-test is part of my article Introducing TurboSignals. It does indeed look like you've made some serious strides in performance. Congrats!

By: jackson

jackson — Tue, 16 Feb 2010 18:31:30 +0000

I hadn't heard about the MATE framework before, but it does indeed look like it uses a lot of events. All of the examples look pretty simple though, so there's probably not much of a performance concern at all. Perhaps a much larger, more complicated MATE application would start to feel the Event/EventDispatcher system pain. Believe me, if you look into how much allocation, deallocation, and the GC work that system produces, you'll see why it's bad to do a lot of it (hundredsper second). A few a second is just fine for a weather widget. :)

By: Arnaud

Arnaud — Tue, 16 Feb 2010 14:15:25 +0000

Very good post ! very interesting.
What is your opinion about the MATE framework which makes an extensive use of Events ?