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

Reply via email to