Don't quote me..
I looked into the source for the first time when blaze rc1 was released.
Its complicated.
On ResultEvent is
override mx_internal function callTokenResponders():void
{
if (token != null)
token.applyResult(this);
}
Apply result is
mx_internal function applyResult(event:ResultEvent):void
{
setResult(event.result);
if (_responders != null)
{
for (var i:uint = 0; i < _responders.length; i++)
{
var responder:IResponder = _responders[i];
if (responder != null)
{
responder.result(event);
}
}
}
}
callTokenResponders is called by abstract invoker which also
dispatchers the result/fault events at the same time
mx_internal function dispatchRpcEvent(event:AbstractEvent):void
{
event.callTokenResponders();
if (!event.isDefaultPrevented())
{
dispatchEvent(event);
}
}
On 07/02/2008, at 4:11 PM, Josh McDonald wrote:
You're right, I hadn't noticed that. That's actually kinda strange.
When are they called, and what actually initiates the responders? Is
it before or after the data or error events are dispatched?
-Josh
On Feb 7, 2008 3:03 PM, Bjorn Schultheiss <[EMAIL PROTECTED]
> wrote:
One thing i don't like about addResponder() is that there is no
removeResponder();
On 07/02/2008, at 4:01 PM, Josh McDonald wrote:
What's the prevailing wind / general thoughts on using
token.addResponder vs adding event listeners, beside the "one
request" vs "all requests" nature of it? Is one faster / better /
more common that the other?
--
"Good people will do good things, and bad people will do bad
things. But for good people to do bad things—that takes religion."
:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]
--
"Good people will do good things, and bad people will do bad things.
But for good people to do bad things—that takes religion."
:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]
