Differences

This shows you the differences between two versions of the page.

Link to this comparison view

admin:indexing:autocomplete:tips [2011/01/24 22:15]
els
admin:indexing:autocomplete:tips [2016/06/28 22:38]
Line 1: Line 1:
-~~NOTOC~~ 
  
-{{page>:​top_add&​nofooter&​noeditbtn}} 
- 
-====== Administration:​ Omnidex Indexing ====== 
- 
-===== AutoComplete ===== 
- 
-[[admin:​indexing:​autocomplete:​home|Overview]] | 
-[[admin:​indexing:​autocomplete:​example|Example]] | 
-[[admin:​indexing:​autocomplete:​sql|SQL]] | 
-[[admin:​indexing:​autocomplete:​optimization|Optimization]] | 
-**[[admin:​indexing:​autocomplete:​tips|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 on 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]]** 
- 
- 
-====== Additional Resources ====== 
- 
-See also:  
- 
-{{page>:​admin:​indexing:​see_also&​nofooter&​noeditbtn}} 
- 
-{{page>:​bottom_add&​nofooter&​noeditbtn}} 
 
Back to top
admin/indexing/autocomplete/tips.txt ยท Last modified: 2016/06/28 22:38 (external edit)