Re: [flexcoders] HTTPService token: a bug or by design?

2010-02-09 Thread Tim Romano 

To answer my own dumb question.

var token: AsyncToken;
token = send();
var myResponder : AsyncResponder= new AsyncResponder(onResult, onFault, 
token);

token.addResponder(myResponder);
function onResult(e:ResultEvent , token:Object=null):void {}



On 2/8/2010 6:05 PM, Tim Romano wrote:


I've run into one bug in the mx.rpc.http.HTTPService class in FB4 beta
2 -- the AsyncResponder's onResult function fires *twice* unless you
wire up a dummy eventhandler. And so I am wondering if the following is
not also a bug:

var myResponder : AsyncResponder= new AsyncResponder(onResult, onFault);
var token: AsyncToken;
token = send();
token.addResponder(myResponder);
function onResult(e:ResultEvent , token:Object=null):void {}

The token parameter is always null in the onResult function. Isn't that
parameter supposed to contain the token to which the Responder was added?

Thanks
Tim Romano

[flexcoders] HTTPService token: a bug or by design?

2010-02-08 Thread Tim Romano 
I've run into one bug in the mx.rpc.http.HTTPService class  in FB4 beta 
2   -- the AsyncResponder's onResult function fires *twice* unless you 
wire up a dummy eventhandler.  And so I am wondering if the following is 
not also a bug:

var myResponder : AsyncResponder= new AsyncResponder(onResult, onFault);
var token: AsyncToken;
token = send();
token.addResponder(myResponder);
function  onResult(e:ResultEvent , token:Object=null):void {}

The token parameter is always null in the onResult function. Isn't that 
parameter supposed to contain the token to which the Responder was added?

Thanks
Tim Romano