--- In [email protected], "trefalgar" <trefal...@...> wrote: > > --- In [email protected], "trefalgar" <trefalgar@> wrote: > > > > --- In [email protected], "Amy" <amyblankenship@> wrote: > > > I always use mx.rpc.Responder instead of AsyncResponder (is that a custom > > > class?). There's a working example of using AsyncToken with AMFPHP here > > > http://flexdiary.blogspot.com/2009/01/lazy-loading-tree-example-file-posted.html > > > . Maybe that will help you see something the docs aren't showing you. > > > > var token:AsyncToken = myService.disableStatistics(user,pass,email,tArray); > > token.info = email; > > token.addResponder(new AsyncResponder(myResults,myFaults,token)); > > I forgot this little bit - using Responder over AsyncResponder. As far as I > can tell, it's not a custom class as it's included by default in the SDK.
I've never used it, but I'm thinking it doesn't look as useful as a regular mx.rpc.Responder. For one thing, it doesn't give you the ResultEvent/FaultEvent. Instead, it gives you some odd sort of info object, that I wouldn't even know how to inspect, as no details are provided as to what that object will look like. > As far as usage, if I use Responder over AsyncResponder, I get the following > error: > > 1067: Implicit coercion of a value of type flash.net:Responder to an > unrelated type mx.rpc:IResponder. Yeah, don't use flash.net.Responder. Use mx.rpc.Responder. That's why I included the full path. > I'll see if I can figure that out, but AsyncTokens definitely don't seem to > like me. Honestly, I'm not sure how it is that you don't see any difference between what I my example shows and what you're doing. My fault/result method signatures are completely different--they have a different number of arguments and expect different data types. These are the kind of details you need to train yourself to pick up on, or you're going to continue to find the documentation unhelpful. Hope this clarifies; Amy
