Timeline for When virtual scrolling/pagination meets incremental search
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2017 at 21:49 | comment | added | Frank Hileman | Most applications like this have a timer that is triggered after each keystroke. If a certain amount of time (may be less than 1 second) has elapsed since the last keystroke, you can then send the request. It is best to have at least some kind of delay, 250 ms or more, before sending the request out. Another trick is to have a minimum delay between requests. | |
| Feb 8, 2017 at 14:30 | comment | added | Mawg | Feel free to post that as an answer. I tend to agree. Sigh! looks like I am going to have to code it &profile it. No way around it :-( | |
| Feb 8, 2017 at 13:53 | comment | added | Joppe | You are asking something noone can give you, it all depends on your render time, how quick your back-end executes these queries. How many users do you have simultaneously? How much infrastructure/money are you willing to throw at this? Etc, etc. Google does real time search on token boundary, not per keystroke. | |
| Feb 7, 2017 at 18:18 | history | asked | Mawg | CC BY-SA 3.0 |