[jQuery] Re: Blocking UI for synchronous ajax calls

2009-09-22 Thread Mike Alsup

> Hi Mike:
>
>    Finally I changed the calls to asynchronous.
>    It looks good now.


The web thanks you.


[jQuery] Re: Blocking UI for synchronous ajax calls

2009-09-22 Thread nomen

Hi Mike:

   Finally I changed the calls to asynchronous.
   It looks good now.

Thanks for your help.

On 16 sep, 10:16, nomen  wrote:
> Hi Mike:
>   Thank you for your answer.
>    I have understand what do you mean between "lock the browser" and
> "block th UI".
>    To test it I have put a sleep in my server (in the function that
> calls the synchronous ajax call ) and I have see that in IE7 and IE8,
> it´s true, but, in FF3, Opera 10, Chrome 2 the browser is not locked.
>    Maybe there is a hack for this? I have written too much code in
> this way (for me, this is the logic way to make it) and I don´t want
> to change it if is not really necessary ;-(
>
> On 15 sep, 12:38, Mike Alsup  wrote:
>
> > >    I have tested BlockUI Plugin but it does not start when I call it,
> > > because I can see with Firebub that the ajax calls are finished when
> > > BlockUI Plugin starts.
>
> > And that is exactly the problem with making synchronous calls to the
> > server - it locks the browser.  I strongly recommend using
> > asynchronous calls instead - I wish the XHR didn't even have a sync
> > API because I don't believe it should ever be used.  Asynchronous
> > programming is only mildly more abstract that synchronous.
>
> > Mike


[jQuery] Re: Blocking UI for synchronous ajax calls

2009-09-16 Thread nomen

Hi Mike:
  Thank you for your answer.
   I have understand what do you mean between "lock the browser" and
"block th UI".
   To test it I have put a sleep in my server (in the function that
calls the synchronous ajax call ) and I have see that in IE7 and IE8,
it´s true, but, in FF3, Opera 10, Chrome 2 the browser is not locked.
   Maybe there is a hack for this? I have written too much code in
this way (for me, this is the logic way to make it) and I don´t want
to change it if is not really necessary ;-(





On 15 sep, 12:38, Mike Alsup  wrote:
> >    I have tested BlockUI Plugin but it does not start when I call it,
> > because I can see with Firebub that the ajax calls are finished when
> > BlockUI Plugin starts.
>
> And that is exactly the problem with making synchronous calls to the
> server - it locks the browser.  I strongly recommend using
> asynchronous calls instead - I wish the XHR didn't even have a sync
> API because I don't believe it should ever be used.  Asynchronous
> programming is only mildly more abstract that synchronous.
>
> Mike


[jQuery] Re: Blocking UI for synchronous ajax calls

2009-09-16 Thread nomen

Hi Mike:
  Thank you for your answer.
   I have understand what do you mean between "lock the browser" and
"block th UI".
   To test it I have put a sleep in my server (in the function that
calls the synchronous ajax call ) and I have see that in IE7 and IE8,
it´s true, but, in FF3, Opera 10, Chrome 2 the browser is not locked.
   Maybe there is a hack for this? I have written too much code in
this way (for me, this is the logic way to make it) and I don´t want
to change it if is not really necessary ;-(





On 15 sep, 12:38, Mike Alsup  wrote:
> >    I have tested BlockUI Plugin but it does not start when I call it,
> > because I can see with Firebub that the ajax calls are finished when
> > BlockUI Plugin starts.
>
> And that is exactly the problem with making synchronous calls to the
> server - it locks the browser.  I strongly recommend using
> asynchronous calls instead - I wish the XHR didn't even have a sync
> API because I don't believe it should ever be used.  Asynchronous
> programming is only mildly more abstract that synchronous.
>
> Mike


[jQuery] Re: Blocking UI for synchronous ajax calls

2009-09-15 Thread Mike Alsup

>    I have tested BlockUI Plugin but it does not start when I call it,
> because I can see with Firebub that the ajax calls are finished when
> BlockUI Plugin starts.

And that is exactly the problem with making synchronous calls to the
server - it locks the browser.  I strongly recommend using
asynchronous calls instead - I wish the XHR didn't even have a sync
API because I don't believe it should ever be used.  Asynchronous
programming is only mildly more abstract that synchronous.

Mike