Re: Is it ever possible for an asynchronous service method's callback to get called without yielding to the browser's event loop?

See the example under "*Non-Blocking / Asynchronous:* " and it gives a clear example addressing Tad's question: http://quickleft.com/blog/142 -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https

Re: Is it ever possible for an asynchronous service method's callback to get called without yielding to the browser's event loop?

Thomas, Yes, I believe that is the answer I was looking for. -Tad -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to go

Re: Is it ever possible for an asynchronous service method's callback to get called without yielding to the browser's event loop?

Derek, Interesting; that makes complete sense with the mock remote service call. So under usual conditions would you say "the expected order" is: 1 - my client-side code executes and makes an async remove service call 2 - my client-side code continues to execute "long-running" code and the async

Re: Is it ever possible for an asynchronous service method's callback to get called without yielding to the browser's event loop?

The only time I encounter what you describe is when I mock the server side code on the client side. In other words, in your code example, I might have myRemoteService actually be an instance of some MyRemoteServiceAsyncMock, that returns dummy data while I wait for someone else to write the server

Re: Is it ever possible for an asynchronous service method's callback to get called without yielding to the browser's event loop?

GWT-RPC makes use of RequestBuilder, which is based on XMLHttpRequest. XMLHttpRequest (XHR) uses events to communicate back with the code, so anything happening on an XHR results in an event being pushed on the event queue, and dequeued by the event loop. Does that answer your question? More de

Is it ever possible for an asynchronous service method's callback to get called without yielding to the browser's event loop?

Is the AsyncCallback framework implemented in such a way that when a RemoteService method is called, is it a GUARANTEE that the browser's event loop will execute at least one cycle before its callback (i.e. onSuccess or onFailure) gets called? For example: ...some code... myRemoteService.myMetho