blocks|key|3512652|text|我会将这些值存储在一个数据库中(您可能会在其中存储他们的用户配置文件)，并在用户登录时将这些值拉入ASP.NET会话。然后，只使用会话中的值作为自动补全值。这样，当用户登录时，您只需访问数据库一次。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3512653|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would store the values in a database (where you are storing their user profiles maybe), and pull the values into ASP.NET Session when the user logs in. Then just use the values from the Session for the auto-complete values. This way you will only have to hit the database once when they log in.

blocks|key|295563|text|Chuck+Norris建议，根据您的JavaScript框架，您可以在进行服务器调用之前构建客户端检查，以查看字段中是否存在给定数量的字符或单词。应该根据给定用户在数据库中输入的信息动态生成XML文件，其中包含针对该用户的自动建议单词。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|295564|根据您尝试构建的应用程序，对特定数据库字段执行全文SQL查询可能更容易。为了提高性能，您可以构建一个cookie，该cookie将由客户端的浏览器缓存，并让您的应用程序在执行完整的数据库查询之前检查更改或检查它是否存在。|295565|Chuck不建议使用会话变量，因为这样会降低应用程序的性能，因为它必须为每个用户在内存中保留这些自动建议的值。|295566|恰克想在他交出我的大脑之前知道你还需要什么。|295567|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Chuck Norris recommends, depending on your JavaScript framework, that you can build client-side checks before making a server call to see if there are a given number of characters or words written in the field. The XML file should be dynamically generated with the auto-suggest words for a given user based on the information entered by that user in the database.

Depending on the application that you are trying to build it may be easier to perform full-text SQL queries on specific database fields. For performance you could probably build a cookie that will be cached by the clients' browser and have your application check for changes or check to see if it exists before performing a full database query.

Chuck does not recommend using session variables because you would degrade the performance of your application because it has to keep those auto-suggest values in memory for each user.

Chuck would like to know if you need anything else before he surrenders my brain.

blocks|key|3512764|text|数据存储|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3512765|您应该将此信息存储在数据库中。为每个字段的每个用户创建一个或两个表，以保存此类信息。|3512766|客户端查询|3512767|当用户开始在文本字段中键入内容时，您可以从客户端(通过AJAX)查询数据库。如果这样做，最好等到字段中至少有3个字符(ish)，然后再向服务器查询建议。这会略微减少请求的数量，并减少客户端和服务器之间的流量。|3512768|我将此方法用于存在大量可能的自动建议命中的字段。|3512769|缓存|3512770|如果您使用此方法，则可以在某些情况下通过缓存响应来优化流程。|3512771|假设查询仅在文本字段中包含3个字符后触发，则可以缓存整个结果。任何进一步添加到文本框中的字符都不会增加返回的结果数。因此，您可以继续过滤缓存的结果。但是，如果用户删除了一个字符，您可以刷新缓存以确保有最合适的自动建议命中。|3512772|服务器端预加载|3512773|在服务器端，收集所有这些数据并将其与页面请求一起发送。(您可以将其作为javascript数组下推到可以在文本字段的onchange事件中引用的某个位置。这样，您就不必进行任何AJAX调用。|CODE|3512774|对于不会有大量可能的自动建议命中的字段，这似乎更好。|3512775|entityMap^0|0|4|0|0|0|5|0|0|0|0|0|0|0|7|0|1M|8|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|19|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1A|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1B|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1C|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1D|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1H|8|@$9|1I|A|1J|B|X]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1K|8|@]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|11|$]]

Data Storage 
You should store this information in a database. Create a table or two to hold this type of information per user per field.

Client-side Query 
You can query the database from the client side (via AJAX) when the user starts to type in the text field. If you do this, it is considered best practice to wait until there are at least 3 (ish) characters in the field before querying the server for suggestions. This reduces the number of requests slightly and the traffic between the client and server.

I use this method for fields where there is a large number of possible auto-suggest hits.

Caching 
If you use this method, you can optimize the process by caching the response in certain situations.

Assuming that the query is fired off only after 3 characters are in the text field, you can then cache the entire result. Any further characters added to the text box will not increase the number of results returned. So, you can just continue to filter down the cached results. If, however, the user deletes a character, you can refresh the cache to make sure that you have the most appropriate auto-suggest hits available.

Server-side Preloading 
On the server-side, gather all of this data and send it along with the page request. (You can push it down as a javascript array somewhere that can be referenced in the <code>onchange</code> event of the text field. This way, you don't have to make any AJAX calls.

This appears to be better for fields where there will not be a large number of possible auto-suggest hits.

I am making an app (asp.net/c#) that will autosuggest a couple fields that users type in. Each user will end up building their own auto-suggest list. Every time they add an item, if it's a new word, it will get added to their list of auto-suggests, just like gmail.

I was wondering how most people go about this? Making a call to the server for every key-press doesn't seem very efficient? Should I make a huge xml file with one entry for each user? An xml file for each user? how would I cache this to make it efficient?

All sorts of questions, but what I am basically looking for is best practices. Thank you.

What approach to take for caching unique auto-suggest lists for users?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在制作一个应用程序(asp.net/c#)，它将自动提示用户键入的几个字段。每个用户最终都会建立自己的自动建议列表。每次他们添加一个条目，如果它是一个新词，它就会被添加到他们的自动建议列表中，就像gmail一样。我想知道大多数人是怎么做的？每次按键都调用服务器似乎效率不是很高？是否应该为每个用户创建一个包含一个条目...

问要为用户缓存独特的自动建议列表，应该采用什么方法？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问要为用户缓存独特的自动建议列表，应该采用什么方法？EN