> I know it but everywhere I have red its recommendet not to use
> asynchronous=false...

Because it freezes the UI (of the whole browser in some cases), which
is usually not what you want.  Since you seem specifically to *want*
to freeze the UI, though, should be just the thing.

But rather than half a half-drawn, frozen UI, if you need all of these
calls to populate it, perhaps you'd be better off having your HTML
show an attractive "Loading one moment" page whilst your asynchronous
XHR calls are collecting the necessary information (perhaps even
showing a progress bar as the various calls complete), and then when
you have everything replace that loading page with the real UI?  That
makes for a nicer experience for the user than something

T.J. Crowder
tj / crowder software / com

On Sep 24, 1:21 pm, buda <[EMAIL PROTECTED]> wrote:
> I know it but everywhere I have red its recommendet not to use
> asynchronous=false, but what should I do in my case?
> On 24 сент, 14:19, ColinFine <[EMAIL PROTECTED]> wrote:
> > On Sep 24, 8:05 am, buda <[EMAIL PROTECTED]> wrote:
> > > I have very complicated interface in which I need to make some
> > > consecutiv Ajax calls to render interface and I need to freze the
> > > interface untile the latest responder will received.
> > If I understand your issue correctly, that is what 'asynchronous =
> > false' is for.
> > Colin
You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to