This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
admin:indexing:autocomplete:tips [2011/01/24 15:29] 127.0.0.1 external edit |
admin:indexing:autocomplete:tips [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| Line 18: | Line 19: | ||
| ==== Implementation Tips ==== | ==== Implementation Tips ==== | ||
| + | The following tips are helpful when implementing AutoComplete in applications: | ||
| + | |||
| + | * It is beneficial to wait until the user has typed two or three letters before triggering an AutoComplete query. This will improve the performance of the query and reduce the number of values to be displayed. | ||
| + | |||
| + | * It is beneficial to transfer the initial AutoComplete results to local memory and then use the local programming language to continue filtering them as more letters are typed. This reduces the number of queries issued to the database and reduces the impact to system resources. | ||
| + | |||
| + | * It can be beneficial to trigger AutoComplete queries on a timer, rather than a letter count. For instance, the first query might be triggered after one second, with refinements to the pull-down box being triggered in subsequent one-second intervals. This allows fast types to not be slowed down by the work of populating the pull-down. | ||
| - | ===== ===== | + | ==== ===== |
| **[[admin:indexing:autocomplete:optimization|Prev]]** | **[[admin:indexing:autocomplete:optimization|Prev]]** | ||