您可以使用在每个组件中出现的分发器。
另外，我们将忽略分发器对象的初步创建过程。
Furthermore, we will gloss over the initial creation of the dispenser object.
本文讨论了用于实现序列号分发器的各种技术。
This article has covered a variety of techniques for implementing a sequence number dispenser.
我们需要对分发器对象进行某些更改，使它能够触发事件。
We need to make some kind of change to the dispenser object so that an event will be fired.
解决这些问题的一个流行解决方案是使用数据库来储存分发器。
A popular solution to these problems is to use a database for holding the dispenser.
如果没有其他人同时更新分发器对象，我们随后的更新仅需一次循环。
If nobody else has updated the dispenser object in the meantime, our later updates will only cost a single round-trip.
这个例子显示了一个内部方法，并假设另一个代码段识别了分发器对象。
This example shows an internal method and assumes some other piece of code has identified the dispenser object.
“消息分发器”模式：EIP组件向一组服务提供者发送消息(多点)。
The "message dispatcher" pattern: the EIP Component sends the message to a list of service providers (multipoint).
您仍然需要多次到达服务器以更新分发器对象或获取usn值。
You're still going to have to make the same number of server round-trips to update the dispenser object or fetch the USN value.
当前在SSIS 2008中已经提供了平衡数据分发器的传输方式。
The Balanced Data Distributor transform is currently only available for SSIS 2008.
现在，我们仅假设所有人都能够连接到ObjectStore并更新分发器对象。
For now, we'll just assume that anyone can connect to the ObjectStore and update the dispenser object.
这对于某些场景非常适用，但如果仅为了访问分发器数据而这样做，显然是过于麻烦。
This may work fine in some scenarios, but generally it would be a lot of bother to do this just to access the dispenser data.
当访问率非常高时，您可能想要使用多个分发器对象，让它们分别负责响应一定范围的值。
At very high volumes, you might like to make things more scalable by having multiple dispenser objects with each one responsible for some range of values.
另一方面，如果两个应用程序轮流更新分发器对象，保留的计数器状态就导致不好的结果。
On the other hand, if a pair of applications is taking turns updating the dispenser, perhaps as some kind of load balancing, that remembered state backfires on us.
限制P8对分发器对象或对象的写访问，从而使一般用户不能绕过servlet更新值。
Restrict P8 write access to the dispenser object or objects so that ordinary users cannot bypass the servlet to update the value.
平衡数据分发器利用并行机制来加快数据传输的速度，因此不会对单处理器的环境产生影响。
The Balanced data Distributor takes advantage of parallelism to speed up data transformations, so it won't have an effect on single-processor configurations.
可以给上面的组合集成增加一个“分发器”集成单元，它负责给“路由”单元和全局监测服务发送消息。
A "dispatcher" integration brick can be added to the previous composite integration to send the message to the "routing" brick and to the global monitoring service.
SQLServer性能团队对于在并行环境中使用平衡数据分发器提供了更多最佳实践信息。
The SQL Server Performance Team provides more information on best practices for using the Balanced Data Distributor in parallel environments.
在下面的例子中，我们假设objectstore的身份和分发器对象的特定位置针对应用程序进行了某些配置。
For the examples that follow, we assume that the ObjectStore identity and specific location of the dispenser object are somehow configured for the application.
首先，在更新objectstore中的分发器对象和执行异步事件处理程序之间存在一段很短的时间。
First, there is a small period of time between the update of the dispenser object in the ObjectStore and the execution of the asynchronous event handler.
由于错误页面是在请求分发器转发之后显示的，FacesContext不再在作用域中，因此这时执行业务逻辑就太迟了。
Because the error page is displayed after a request-dispatcher forward, the FacesContext is no longer in scope and it is therefore too late to do any business logic.
在使用基于P8的分发器对象时，获取序列号的方法在本质上是一样的：读取旧值、更新并储存新值，然后将新值返回给调用方。
When using a P8-based dispenser object, the conceptual idea for getting a sequence number is the same: read the old value, update and store the new value, and return the new value to the caller.
配置拥有RunAs角色的servlet，它具有更新分发器对象所需的CE权限(参见使用J2EE servlet侧栏)。
Configure the servlet with a RunAs role that has CE rights to update the dispenser objects. (See the Using a J2EE servlet sidebar.)
查找分发器对象的两种常见方法是使用预定义的ID值或将对象储存在ObjectStore 内部的预定义路径中。
The two popular techniques for locating the dispenser object are to use a predefined ID value or to store the object in a predefined path within the ObjectStore.
作为实现该目的的一次性设置的一部分，我们定义一个新的定制事件，并将其持久化在保存分发器对象的ObjectStore中。
So as part of the one-time setup for all of this, define a new custom event and persist it in the ObjectStore holding the dispenser object.
在此模型中设计了翻译器、分发器、集成器，分别用于数据的格式转换、分解和合并，并对模型实现过程中的关键技术给出了详细描述。
In this model, designed interpreter, dispatcher, integrator used for data format change, data decomposition and data combination, and DE - scribes the important technologies of realizing process.
如果您想将您自己的架构添加到验证器提供的架构中，请将验证器分发的.schema文件复制到您配置的目录中。
If you wish to add your own schema to those already provided with the validator, copy the.schema files distributed with the validator to the directory you configure.
第三，服务器能够分发打印机驱动程序，如果需要的话。
And third, the server can distribute printer drivers, should they be needed.
事件服务器概要设置定义了CEI服务器的持久性和分发行为。
The event server profile Settings define the persistence and distribution behavior of the CEI server.
事件服务器概要设置定义了CEI服务器的持久性和分发行为。
The event server profile Settings define the persistence and distribution behavior of the CEI server.
应用推荐