Re: =[xhr]

• From: Tab Atkins Jr. <jackalmage@gmail.com>
• Date: Tue, 28 Apr 2015 13:42:26 -0700
• To: Ken Nelson <ken@pure3interactive.com>
• Cc: public-webapps <public-webapps@w3.org>
• Message-ID: <CAAWBYDDdzVFDPacV+j7itoBMfLbTGXiE6JU09aTat+cViv7o_w@mail.gmail.com>

On Tue, Apr 28, 2015 at 7:51 AM, Ken Nelson <ken@pure3interactive.com> wrote:
> RE async: false being deprecated
>
> There's still occasionally a need for a call from client javascript back to
> server and wait on results. Example: an inline call from client javascript
> to PHP on server to authenticate an override password as part of a
> client-side operation. The client-side experience could be managed with a
> sane timeout param - eg return false if no response after X seconds (or ms).

Nothing prevents you from waiting on an XHR to return before
continuing.  Doing it with async operations is slightly more complex
than blocking with a sync operation, is all.

~TJ

Received on Tuesday, 28 April 2015 20:43:13 UTC