I wrote a loading mask that creates a transparent mask over the window to stop input. After a second or two an animated loading message fades into view. That way if the request is quick you don't get a message flashing on and off.
On Jul 21, 3:36 pm, cokol <eplisc...@googlemail.com> wrote: > ...in that case it would be an option to show up a modal dialog asking > the user to get some coffee :-) > > @mk > youre welcome! > > On 21 Jul., 20:20, Brian Reilly <brian.irei...@gmail.com> wrote: > > > > > Could you get the same effect by preventing user input during your > > server request, either by finding all of the controls/links and > > disabling them or overlaying something that receives and swallows all > > events? At least that way, you're not locking up the browser > > completely. Is there some other functional requirement that makes > > synchronous requests a requirement? > > > -Brian > > > On Jul 21, 12:00 pm, mk <munna.kaka.ch...@gmail.com> wrote: > > > > I understand that asynchronous is the way to go and sometimes we > > > change UI design just to support async. But atleast in our project, > > > there are functional requirements where sync is the only solution. > > > (BTW: sync is not as bad. I understand that javascript in browser is > > > single threaded but it's used by a single user to do a single task. > > > And if sync response is required to meet functional need than we got > > > to do sync. It does not effect scalability of whole app ) > > > > Anyway any body used any hack to support sync. > > > (Is JSNI the only way to go?) > > > > On Jul 21, 9:10 am, Nathan Wells <nwwe...@gmail.com> wrote: > > > > > 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 <dim...@gmail.com> 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 <prakash.masilam...@gmail.com> 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 <munna.kaka.ch...@gmail.com> 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- Hide quoted text - > > > > > - Show quoted text - -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
