In this section, you'll see how to generate keys that let you store data for each user session.
在这一部分中，您将看到如何生成键，让你存储每个用户会议所用的数据。
In this section, you see how to generate keys that let you store data for each user session.
在这一部分中，您将看到如何生成为每一个用户会话存储数据所用的键。
This is common in many testing scenarios, enabling user data to hang around in memory until the user session times out, or until any caches in use get refreshed.
在许多测试场景中，这是很常见的，允许用户数据挂起在内存中，直到用户会话超时，或者直到刷新正在使用的任何缓存。
Avoid replicating data into the session that can be recreated from sources other than through user interaction.
避免将可以通过用户交互之外的其他源重新创建的数据复制到会话中。
There are numerous use cases for caching by user session, and they are often based on different components operating on the same backend data.
对于通过用户会话进行缓存，有许多用例，它们通常基于对同一后端数据进行操作的不同组件。
Pessimistic session locking should be used with great discretion, as it serializes access to data across a business process that includes user think time.
必须谨慎使用悲观会话锁定，因为它在业务流程（包括用户思考时间）中序列化数据访问。
But I will give you a hint: Think more carefully about the user session data.
但我会给你们个提示：仔细思考一下用户会话数据。
IMS allows operators to charge multimedia session appropriately: If a user USES videoconference over the 3g cellular network, there is usually a large data transfer that consists of audio and video.
IMS允许运营商对多媒体会话进行适当收费：如果用户通过3G移动网络使用了视频会议，则通常会产生包含音频和视频的大量数据传输。
J2EE applications typically store this kind of data in in-memory session objects for better performance and for a better user experience.
J2EE应用程序通常将此类信息存储在内存中的会话对象中，以实现更好的性能或实现更好的用户体验。
Wait a minute… where are we going to store the user session data?
等等...我们要把用户会话数据存放在哪儿？
Your EJB layer should be a stateless service fronted by a stateless session bean, so it cannot store user data such as a username or password.
您的ejb层应当是无状态的服务，该服务由无状态的会话bean来负责管理，所以不能存储用户的数据，如用户名或密码。
By collecting data about a user throughout a session, we are able to create a profile of that user, and then use that profile to personalize his or her experience.
通过从一个会话全面地收集有关一个用户的数据，我们可以为那个用户创建一个简要表(profile)，然后使用这个简要表来个性化他的用户体验。
User registration, profile, session data.
用户注册、个人资料、会话数据。
Data can be stored in the session with no direct way for a malicious user to alter it. (Bugs in your code may still give an attacker an opening, of course.)
数据可以存储在会话中，恶意用户无法直接修改它(当然，代码中的bug仍然可能产生安全漏洞)。
Session data is that which has a lifetime of the user session, and is created based on actions the user performed that translate to processAction calls on the portlet.
会话数据具有用户会话的生存期，是基于用户执行的操作（将转换为 Portlet 中的 processAction调用）创建的。
The framework can then restore the continuation from the session before each new request, using the same approach that you used to store user data.
然后，框架可以在处理每个新请求之前从会话中恢复延续，采用的方法与存储用户数据一样。
The life span of the data saved to a session is, at most, from the moment the user accesses a domain to the moment when a user times out after a preset amount of time of inactivity.
保存在会话中的数据的生命期，最长是从用户访问域的那一刻到用户在预设的一段不活动时间之后超时的那一刻。
The clandestine owner of the existing session-the hacker-can, at this point, record and exploit data that is transferred between the new user and the server as long as the session remains active.
现有会话的秘密所有者—那个黑客—此时能够记录和利用在新用户和服务器之间传输的数据，前提是会话保持活动。
To avoid leakage that stems from document transparency, you might end up with a need-to-know system that isolates XML data sets by user session and not just by application.
为了避免由于文档透明性而产生的信息泄漏问题，您最终可能需要使用按照用户会话来隔离xml数据集的“需要了解”的系统，而不仅仅是按照应用程序来隔离xml数据集的系统。
Portlet implementers can use preferences to store and retrieve data across an end-user session with the portal.
Portlet实现人员可以使用首选项在门户的最终用户会话中存储和检索数据。
You don't see any of the normal tedious code to support the Back button, or to save user data to the session — that's all encapsulated into Cocoon's framework.
这里没有支持Back按钮或者将用户数据保存到会话中所需的冗长代码——这些都封装在Cocoon的框架中了。
It is essential that you use a different instance of Chrome for the remote session and that is why we run it with the — user-data-dir argument.
远程会话必须使用不同的Chrome实例，所以运行时要加——user - data -dir参数。
You should also avoid displaying truly sensitive data, such as credit card Numbers, to a user who has only been validated by session id.
你也应当避免直接向一个仅通过会话id验证的用户显示高度敏感的数据，例如信用卡号。
Combined the examples, data cleaning, user identification, session identification, path completion and transaction identification are discussed deeply.
结合实例详细介绍了数据净化、用户识别、会话识别、路径补充和事务识别等数据预处理技术。
Data preprocessing is to treat these redundant information such as data purifying, user recognition, session recognition and pathway complement.
数据预处理就是处理这些冗余信息，经过数据净化、用户识别、会话识别、路径补全操作后得到能够用于挖掘的数据。
Chapter 3 introduces the processes of data preprocessing, they are data cleaning, user identification, user session identification, path supplement and data formatting.
第三章探讨了数据预处理的流程，即数据清理、用户识别、用户会话识别、路径补充和数据格式化。
Then improves the user session identification and path identification which are the processes of the data preprocessing.
针对预处理步骤中的用户会话识别和路径填充进行了相应的改进。
Instead of saving article content for each user session, the site can use smarter data access so that only one copy of each article is cached on the server, and session state usage is minimized.
与其储存每个使用者工作阶段的文章内容，该网站可以使用更聪明的资料存取方式，以便在伺服器上只快取每篇文章的一份复本，这样就可以将工作阶段状态的使用量降到最低。
Instead of saving article content for each user session, the site can use smarter data access so that only one copy of each article is cached on the server, and session state usage is minimized.
与其储存每个使用者工作阶段的文章内容，该网站可以使用更聪明的资料存取方式，以便在伺服器上只快取每篇文章的一份复本，这样就可以将工作阶段状态的使用量降到最低。
应用推荐