--- In flexcoders@yahoogroups.com, "byte.sensei" <[EMAIL PROTECTED]>
wrote:
>
> OK, so I understand that Flex web service calls are asynchronous,
and I
> understand the many cases where this makes sense since you don't
have
> to hold up the UI experience while waiting for a web service or
rem
I actually agree with you. Having a synchronous call would make life
so much easier in many places. Yes, there are always ways to code
around it. But, if I have a situation where I don't want the user to
do anything else, or any more logic to be run until I get the answer
back from the server, t
Resistance is futile.
Tracy
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of byte.sensei
Sent: Tuesday, April 29, 2008 10:58 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Synchronous web service calls
Thanks for the
Thanks for the replies. This is (sort of) the direction I was headed,
although I like your specific idea below. I guess I'm still holding on
to the synchronous world of coding I came from. ;) I feel like I'm
always having to come up with ways to deal with Flex's asynchronous
behavior, and it
Of jerusalem_pilgrim
Sent: Tuesday, April 29, 2008 10:13 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Synchronous web service calls
Why can't you just use a "web service calls" counter in your code?
Every time a request goes out, increment it, every time you
Why can't you just use a "web service calls" counter in your code?
Every time a request goes out, increment it, every time you get a
response, decrement it. The "Print Receipt" button only gets enabled
if the counter is back to 0.
--- In flexcoders@yahoogroups.com, "byte.sensei" <[EMAIL PROTECT
6 matches
Mail list logo
