Well, honestly I didn't spend too much time on thinking which way would
be better, sync or async.
I think I used sync requests because the hourglass appears and the user
know they have to wait a little. If I recall correctly I also had some
problems getting async requests to work correctly on some browsers.
Lee, do you think async requests are better? Can you explain why?
Thanks, Josias
In ie it seems that the lenya menu bar at the top of the page disappears and
then "distorts" briefly during any subsequent httpxmlrequests. I'm guessing
that async would help prevent this.
Subsequent requests after the initial tree population may not need any
visual cue to the user as its speedy enough to be related to the user action
of clicking the + image on the menu. They will "allow" a small time delay.
The w3c site claims that asnc is preferable as on error or transport delays
won't lock the browser. (Although I think they are asuming that the request
is doing background stuff and displaying the site tree might not be
classified as this ??)
Instead of the hour class an alternative could be a menu status area which
could read (loading.... etc).
More importantly well done on writing the most impressive rocket science
javascript I've ever saw.
Lee C
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
