|
Nathan,
well in EXT JS it isn't really a problem because the XHR is first fired
when you stop typing
On Mon, Jul 16, 2012 at 5:50 PM, Nathan Andelin <nandelin@xxxxxxxxx>wrote:
From: Henrik Rützou
Nathan, why do you want to queue them, I have no problem with firering
a lot of XHR's at the same time!
Well, we were talking about browsers having a limit on the number
concurrent XHR connections, so I suggested queuing. But one other benefit
is that you can be assured that requests that are fired off as a result of
keypress events are answered in the order received.
Say, the server is performing predictive fetch based on keyPress events.
If the user types:
ABC ...
You don't want the server to respond with a list of strings beginning with
ACB ...
You want the keystrokes processed in the order keyed.
-Nathan.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
--
Regards,
Henrik Rützou
http://powerEXT.com <http://powerext.com/>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
