The way I think of it is that you are asking a server a question and
receiving either a fault or a result. When you get a result, you
generally need to massage the data returned so you need to tell Flex
which function will handle the resultant data.

So the result="myResultHandler()" says to me: When a result is
returned, send the resultant data off to this function to do something
with it.



--- In [email protected], "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> 
wrote:
>
> Ok how about "onsuccess" and "onfailure"
> 
> The "result", to me is what the service returns, not the function that 
> is used if the service returns a result. So result="myResultHandler()" 
> seems to me like you are telling the service what to return, which 
> doesn't make any sense, and furthermore it seems like the name of the  
> function you are using for that, ("myResultHandler()")  also doesn't 
> make any sense.
> 
> onsuccess="myResultHandler()" does make sense.
> 
> 
> 
> 
> Amy wrote:
> >
> > --- In [email protected] 
> > <mailto:flexcoders%40yahoogroups.com>, "info1@" <info1@> wrote:
> > >
> > > Josh McDonald wrote:
> > > Yes I ended up doing that, but I was originally looking for was
> > some
> > > MXML that would do something like this:
> > > urlLoader.addEventListener(Event.COMPLETE, onComplete);
> > > as in "completelistener="myResultHandler()"
> > >
> > > but i realize now that I was wrong.
> > >
> > > I looked at that page many many times but had no idea what
> > the "result"
> > > tag attribute was supposed to do, and no idea how to go about
> > finding
> > > out I think "result" is the wrong word. "oncomplete" would make a
> > lot
> > > more sense.
> >
> > The problem with having only one onComplete event is that there is
> > not just one thing that can happen. There is a result event for when
> > the service returns successfully and a fault event for when it fails.
> >
> > HTH;
> >
> > Amy
> >
> > 
> > No virus found in this incoming message.
> > Checked by AVG - http://www.avg.com 
> > Version: 8.0.138 / Virus Database: 270.4.10/1551 - Release Date:
7/14/2008 6:49 AM
> >
>


Reply via email to