On 08/13/2010 09:16 AM, Kevin Qiu wrote:
>
> Do not put code at //1 or //2 Did my example show that? I don't
> think it did. //1 and //2 should be inside the SM. Did you code an
> implementation or just do a desk check?
>
>
> The whole point of syncing a series of async calls is to make the flow
> of execution deterministic. I put print statements there just to show
> the execution order. The execution order desired is:
> // 1
> async calls
> // 2
> return
> That's the objective I want to achieve and no offence, I don't think
> that's what your implementation does.
It does. As I noted earlier, the position of those code fragments won't
provide the behavior you seek. The fragments must be part of the SM
logic. Placing them where you did simply {ignores | doesn't follow} my
advice.
To correct your example:
code fragment "//1" goes in the body of INITIAL state. This message will
print once.
code fragment "//2" goes in the body of the DICTIONARYREAD state. This
message will print for each element in the execute queue.
code fragment "//3" (not shown) goes in the body of the FINAL state.
This message will print once.
> I sent you my gmail address.
Received.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
