Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeder2.ecngs.de!ecngs!feeder.ecngs.de!border1.nntp.ams.giganews.com!nntp.giganews.com!xlned.com!feeder1.xlned.com!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <1372953269.FrdeS7i7de@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Thu, 04 Jul 2013 16:26:39 +0200 User-Agent: KNode/4.10.4 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. MIME-Version: 1.0 Lines: 54 NNTP-Posting-Date: 04 Jul 2013 16:26:42 CEST NNTP-Posting-Host: f3a7861c.newsspool4.arcor-online.net X-Trace: DXC=a>9mNGM@:AR5TOT9_N5ia>_ X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:20546 Bart Van der Donck wrote: ^^^^^^^^^^^^^^^ Wrong, see RFC 5536 and . > saurabh...@gmail.com wrote: >> I am trying to make 2 ajax calls on a button click in >> javascript. The response of the first web service will >> decide whether the second ajax calls should be made or >> not. When I am trying to call the second web service >> in the success function of the first one, I am able to >> get the response but the HTML UI freezes. But if I >> make a single ajax call and displays its response, it >> works fine. > > Some ideas: > > 1. You're talking about calling [cit.] "the second web service in the > success function of the first one". This is not recommended; Wrong. > it is better to cleanly finish the first AJAX-function before proceeding; That has happened when the “success function of the first one” is called. > 2. A 'setTimeout()'-function *might* *maybe* help; Wrong. A setTimeout() call will increase the risk of a timing problem as you can never know how long it takes to receive and process the first response. Using the event listener is the safe approach. > 3. Common 'XMLHttpRequest'-techniques typically use some variables. You > would want to make sure that none of those are repeated in the second > function, Wrong. Instead, it is wise to reuse variables that are no longer used. > and that their scoping is correct; Correct. A common mistake is to use the same XHR object twice, while the response handling for the first request with that object is still in progress. XHR libraries like JSX:http.js implement approaches that prevent that from happening. > 4. Not to say that AJAX is bad, but similar techniques exist which form > IMHO certainly a good alternative, such as iframes or server-side logic. Utter nonsense. -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.