There is only one case I know of where synchronous should be used: when you want to do a server call and get a response when the user is leaving the page. If you don't use synchronous here, you will fail to get the response from whatever asynchronous call you made when the page exits.
On Jul 21, 8:14 am, Dimitrijević Ivan <[email protected]> wrote: > It is strongly recommended to avoid using AJAX on synchronous way! > Remember that A in AJAX is for Asynchronous. So you should consider > and use this as a feature not as a problem. > > Using AJAX on Synchronous way is a very common anti pattern in AJAX > programming. > > On Jul 20, 9:09 pm, Prakash <[email protected]> wrote: > > > > > Its not possible with GWT. > > > refer below > > link.http://code.google.com/webtoolkit/doc/latest/FAQ_Server.html > > > Regards, > > Prakash M. > > > On Jul 20, 10:06 am, mk <[email protected]> wrote: > > > > How to make an GWT AJAX call Sync (instead of async) > > > > billion years back we used to use a flag as below. how to do it from > > > GWT. > > > > AJAX.open("GET", url, false); > > > > It's just that for a particular requirement we have to have call sync -- 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.
