Blocking I/O on the main thread is ok if it's possible to specify
a timeout for the I/O operation, see:
http://www.openajax.org/runtime/wiki/Synchronous_XHR_Enhancements
and if the UA'a user interface is kept responsive (running animated
GIFs, repainting UI etc) and allows the user to abort the
From the link you provide:
In some situations, it is more natural to make a blocking call and
have the call return the received value, but this synchronous-style
XHR is currently plagued with the risk of locking up the user's
browser window forever as there is no timeout used in waiting
On Wed, Jul 9, 2008 at 6:44 PM, Aaron Boodman [EMAIL PROTECTED] wrote:
I still think you should be able to pass JSON-style objects between
workers without needing to do the serialization yourself.
A big +1 to allowing JSON-compatible objects as worker messages. I
left that feature out of the
