Multicast streams are created orderly according to service queue priority value and fewer multicast streams are needed for the large scalable video-on-demand service.
根据服务队列的优先级，顺序地建立主流，并且在大规模视频服务中只需少量的主流。
On the other hand, the service might have problems connecting to the queue manager or accessing its initiation queue.
另一方面，此服务可能拥有连接到队列管理器或访问其发起队列的相关问题。
All that is required is to place the service under queue manager control and then to start it.
所需的所有操作是将服务放置在队列管理器控制之下，然后启动它。
This is what we characterize as elasticity, making the asynchronous service framework an elastic queue.
这就是我们所说的弹性特征，这使得异步服务成为一个弹性队列。
All the servant regions are now bound to existing work queues, and no servant region can immediately convert to the new service class work queue.
现在所有服务区域均绑定到现有工作队列，没有任何服务区域能够立即转换到新的服务分类工作队列。
Destinations are logical addresses which can have the behavior of a service endpoint, a queue, or a topic.
目的地是一些可以具有服务端点、队列或者主题的行为的逻辑地址。
Currently, there is no standard service for returning a pair of queue addresses, so the consumer must just know the addresses.
目前，没有用于返回队列地址对的标准服务，所以使用者必须确切地知道这些地址。
This ties the queue name to the service registry and the logical application layer.
这将队列名称与服务注册中心和逻辑应用程序层绑定在一起。
This queue is named for the service that it represents and not the application providing the service.
此队列按它所表示的服务命名，而不是按提供该服务的应用程序命名。
Each broker instance can be started as an MQ service, so that when the queue manager fails over to the standby, the broker is automatically started.
每个代理实例可以启动为一个MQ服务，从而在队列管理器故障转移到备份代理时自动启动该代理。
Basically, at any given time, any servant region will only bind to a single specific service class work queue and select requests from there.
本质上，在任何给定的时间，任何服务区域将仅绑定到单个特定的服务分类工作队列，并从该队列选择请求。
It can only browse messages on queue destinations hosted by the service integration bus to which it is connected.
它只能浏览其所连接到的服务集成总线承载的队列目的地上的消息。
The queue manager executes one service request within a queue at a given time to maintain integrity.
队列管理器在给定的时间仅执行某个队列中的一个服务请求，以维持完整性。
The work queue mechanism is inherited from the WLM queuing manager service.
工作队列机制是从wlm队列管理器服务继承而来的。
This allows to multiplex multiple service accesses over a single queue.
这可以支持在单个队列上复用多个服务访问。
The service consumer needs only a reply-to queue, which can be an anonymous dynamic queue or a predefined static queue.
服务使用者只需要一个应答队列，该队列可以是匿名的动态队列或预定义的静态队列。
This queue keeps track of which service requests to execute.
此队列跟踪要执行哪些服务请求。
The caller puts a request message on the request queue for the service and then (asynchronously) listens for the result on the reply queue.
调用方将请求消息放在服务的请求队列中，然后(异步)侦听应答队列中的结果。
A new request comes in and stays in the new service class work queue.
新的请求传入并滞留在新的服务分类工作队列中。
In the case of a JMS-based service, one queue can be reused for multiple operations.
对于基于JMS的服务，可以对多个操作重复使用一个队列。
In the panel shown in Figure 11, there are two servant regions bound to the same service class work queue, CBDEF.
在如图11所示的面板中，有两个服务区域与同一个服务分类工作队列CBDEF绑定。
In an SOA implementation, the only well-known queue is the one that represents the service endpoint.
在SOA实现中，唯一众所周知的队列是表示服务端点的队列。
Figure 8 shows the message queue approach applied to service invocation, specifically our stock quote service.
图8显示了应用到服务调用的消息队列方法，其中的细节以我们的股票报价服务为例。
A main thread will listen to the buffered queue and will service the requests it receives.
主线程会侦听缓冲队列，并服务其接收的请求。
Amazon has another notification service, Simple Queue service (SQS), using a polling-based approach to messaging.
亚马逊还有另一项通知服务，称为简单队列服务，简称SQS，采用轮询的方式处理消息。
This MDB will subscribe to the Queue, in which our Web service will put the messages.
此MDB将订阅队列，而我们的Web服务会将消息放入到此队列中。
When the RMSender finds the web service response available in the Queue, it returns this response to the client application.
当RMSender在Queue中找到可用的Web服务响应时，它会将此响应返回给客户机应用程序。
One "queue" Destination for the Inbound service.
一个入站服务的“队列”目的地。
If you have only one running instance of the Index Update Service, then multiple tasks will queue until the executing task completes.
如果您只有一个IndexUpdateService的运行实例，那么多个任务将会排队等待，直到执行任务完成。
If you have only one running instance of the Index Update Service, then multiple tasks will queue until the executing task completes.
如果您只有一个IndexUpdateService的运行实例，那么多个任务将会排队等待，直到执行任务完成。
应用推荐