第一个Cognos分派器的别名。
这将把调用进程的主线程转换为控制分派器。
This transforms the main thread of the calling process into the control dispatcher.
这意味着源和目标分派器uri将是相同的。
This means that both Source and Target dispatcher URIs will be the same.
db2d is p：客户连接集中分派器。
另外9个可能存在的Cognos分派器的别名。
Instance2作为网关、分派器和内容管理器。
Instance 2 plays the gateway, dispatcher, and content manager role.
像下面演示的那样，对目标和源使用相同的分派器uri。
Use the same dispatcher URI for both the target and the source as illustrated below.
实际上，在分派器列表中添加云实例，就能动态地扩展解决方案。
Essentially you are dynamically scaling out your solution by adding cloud instances to the dispatcher list.
负载均衡器将请求路由到基于分派器的负载均衡标准所选中的内容主机。
The load Balancer routes the request to the content host selected on the basis of the Dispatcher's load-balancing criteria.
这样做不是很耗内存和CPU资源，因此克隆分派器并不会付出很大代价。
Doing so is inexpensive in memory and CPU resources, so there is no significant penalty for cloning dispatchers.
精调的传播控制方式就是使用分派器的. next _ method方法。
The fine-tuned way of propagating control is with the.next_method method of a dispatcher.
但是为了一致性，每次调用分派器都会返回一个从控制传播内容的所有函数中返回的返回值列表。
For uniformity, however, every call to a dispatcher returns a list of return values from all functions that control what was propagated to.
由于传播采用有状态方式跟踪调用了哪些(依次不太特定的)规则，所以分派器不是线程安全的。
Because of the stateful way propagation tracks which (successively less specific) rules have been called, a dispatcher is not thread safe.
不过请回忆一下：通过请求分派器进行转发是在服务器端实现的，而重定向却是由浏览器来执行的。
Recall, however, that forwarding through a request dispatcher is implemented on the server side, while redirects are performed by the browser.
这个解决方案的优势是同构性(仲裁、节流器和分派器都运行在相同的环境中)和高性能设计(完全同步)。
Advantages of this solution are homogeneity (the mediations and the throttler and dispatcher both run in the same environment) and high-performance design (entirely synchronous).
分派器列表作为负载平衡器，Cognos8按分派器在Cognos配置中出现的次序联系它们。
The dispatcher list ACTS as a load balancer so that Cognos 8 will contact the dispatchers in the order they appear within Cognos configuration.
根据以上针对WebSphereES b节流器和分派器的需求，有四种解决方案设计可供考虑。
Given the above requirements for a WebSphere ESB throttler and dispatcher, four solution designs were considered.
调用分派器需要一个分派参数，或者您可以使用 .with_dispatch() 这一便利方法。
The call to the dispatcher either needs a dispatch argument, or you can use the .with_dispatch() convenience method. For example
就像您有时想对继承方法中的超类方法进行调用一样，您有时还想在分派器内对不太特定的规则进行调用。
Just as you sometimes want to call on superclass methods in an inherited method, you also sometimes want to call on less specific rules within a dispatcher.
节流器和分派器被实现为为WebSphereESB提供服务的数据库，其中逻辑被实现为存储过程。
The throttler and dispatcher is implemented as a database with logic implemented as stored procedures to service WebSphere ESB requests.
对于这个示例，10个分派器的限制(这个拓扑中的实例总数为12个)是随意设置的；可以根据需求降低或提高。
The limit of 10 dispatchers (for a total of 12 instances in this topology) was arbitrarily set for this example; it can be lowered or raised based on your requirements.
对Instance2的hosts文件做以下修改，让Instance 2作为网关、分派器和内容管理器。
Assign Instance 2 to the gateway, dispatcher, and content manager role by making the following changes to the Instance 2 hosts file.
SpringMVC分离了控制器、模型对象、分派器以及处理程序对象的角色，这种分离让它们更容易进行定制。
Spring MVC separates the roles of the controller, the model object, the dispatcher, and the handler object, which makes them easier to customize.
无需深入研究分派， multimethods.Dispatch类将为给定分派器调用选择“最合适”的分派。
Without needing to think about dispatch further, the multimethods.Dispatch class will select the "best fit" for a given call to a dispatcher.
负载均衡器可以与服务器安放在同一台机器上，因为服务器是用来装载均衡请求的。这种并置适合于负载均衡器的分派器和站点选择器(Site Selector)组件。
Load Balancer can reside on the same machine as a server for which it is load balancing requests; this collocation applies to the Dispatcher and Site Selector components of load Balancer.
在本文的稍后部分中，您将通过创建执行简单分派的选择器来尝试此操作。
Later in the article, you will try this out by creating a selector that performs a simple dispatch.
从本质上讲，任何进程或线程都可以分派到任意处理器上运行，但绑定在特定处理器上运行的处理器或线程除外。
Essentially, any process or thread can be dispatched to run on any processor, except for processors or threads that are bound to run on a specific processor.
从本质上讲，任何进程或线程都可以分派到任意处理器上运行，但绑定在特定处理器上运行的处理器或线程除外。
Essentially, any process or thread can be dispatched to run on any processor, except for processors or threads that are bound to run on a specific processor.
应用推荐