Derrell Lipman wrote:
>
>> Hi, Derrell.
>> Sad to say, there are a lot of problems which can be solved via sync
>> calls
>> very easy.
>> And they become too complex via async calls.
>> For example, dynamic loading qx class before creating instance (sorry if
>> I
>> bring up old topics).
>> Besides the native AcitveX sync request works well in IE.
>
> Yes, I combined my thoughts from two different threads but you may not
> have read the other one. In a different thread pertaining to the same
> issue, I suggested that as awful as sync calls are and regardless of
> how badly we'd like to eliminate them, we could not get rid of sync
> calls functionality; that people were using it. I also suggested that
> we wanted to try to remove usage of native sync calls, we would have
> to provide a compatibility function that implemented a sync call using
> async requests.
>
> BTW, using the generic Finite State Machine class in qooxdoo, you can
> very easily eliminate the complexity of async calls. You may want to
> take a look at it.
>
> Cheers,
>
> Derrell
>
Hi!
I see you added new feature - split packages loading.
Can you give example, or explane how to use FSM and async requests together
for scripst loading?
Thanks.
--
View this message in context:
http://www.nabble.com/qx.io.remote.Request-doesn%27t-work-in-synchronous-mode-properly-in-0.7-Qx.-tf4028864.html#a11459292
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
