它们分别是消息队列框架接口包中每个抽象类和接口的实现。
These are the respective implementations of each abstract class and interface in the message queue framework interface package.
这些类还可以处理输出队列和后台打印文件，回答后台打印文件的消息，执行其他打印相关任务。
These classes can also work with output queues and spooled files, answer messages for spooled files and do other print related tasks.
这些打印类用于检索后台打印文件、输出队列、打印机以及其他打印资源的列表。
These print classes are used to retrieve lists of spooled files, output queues, printers, and other print resources.
第二类，即本地定义的资源，包括应用程序队列、通道和主题等。
The second category, resources that you define locally, includes things like application queues, channels, and topics.
这意味着，这两类请求都会在队列中花费一段时间，但是gold请求排队的时间比例比较小。
This means that both types of requests will spend some time in the queue, but the gold requests will be queued for proportionately less time.
抽象类BundleMessage标识与消息队列关联的消息并提取其通用功能。
Class BundleMessage identifies a message associated with a message queue and abstracts its common functions.
在MQCON n类中为队列管理器定义了4个不同的概要文件。
There are four different profiles defined for a queue manager in the MQCONN class.
通过调用 message_queue类的receive方法从队列获取消息。
The individual messages are obtained from the queue by calling the receive method of the message_queue class.
这些类还允许访问关于消息队列上的某条消息的信息。
The classes also allow access to information about a message on a message queue.
下面的类是一种常见的并行实用程序模型：任务队列。
The following class is a model of a common concurrent utility: a work queue.
下一个主题是如何定义这些类中的配置文件来保护队列管理器及其资源。
The next topic is how profiles in these classes can be defined to protect a queue manager and its resources.
这些类是具有无等待端的队列，在这里，一个NHRT可以请求读或写某些数据(具体取决于类)，而不存在阻塞的风险。
These are queues that have a wait free side where an NHRT can request to read or write some data (depending on the class) without the danger of blocking.
另一个常见的线程模型是为某一类型的任务分配一个后台线程与任务队列。
Another common threading model is to have a single background thread and task queue for tasks of a certain type.
在旧的规范下，必须专门为队列或主题编写应用程序代码，因为类本身是特定于域的。
Under the older specification, the application code had to be written specifically for queues or topics because the classes themselves were domain-specific.
逻辑工作线程从队列中渠道任务，进行处理，并通过使用一些类提供的函数将结果返回。
The logical workers take the job from the queue, and process it and send back the result by using some of the functions provided by the class.
本部分介绍消息队列框架的主要功能和特性，描述主要类和方法，并提供如何使用框架的示例。
This section describes the major functions and features of the message queue framework, describes major classes and methods, and provides an example of how use the framework.
例如，对于队列，使用一个MQQUEUE概要文件来控制对该队列的访问，但是mqadmin类中的其他概要文件用于控制上下文和用户安全性。
For example, for a queue, an MQQUEUE profile is used to control MQI access to the queue, but other profiles in the MQADMIN class are used to control context and alternate user security.
通过消息队列基础设施的数据可以大致分为两类：查询和业务关键型数据。
Data that passes through a message queuing infrastructure can be broadly separated into two categories: query and business-critical.
mqadmin类中的其他概要文件控制命令资源的安全性，即定义具有特定名称的队列的权限，例如任何以app 1开头的队列。
Then additional profiles in the MQADMIN class control command resource security, that is, the authority to define queues that have a specific name, for example any queues that begin with APP1.
MQ cmds类中的概要文件控制对DEFINEQLOCAL等命令的访问，这些命令用于定义和修改队列。
Profiles in the MQCMDS class control access to commands (such as define QLOCAL) that provide the ability to define or alter a queue.
为了避免无限循环，IBM的jms类会检查消息的恢复计数以及输入队列的恢复阈值和恢复队列属性。
To prevent an infinite loop, IBM's JMS classes inspect the message's backout count, as well as the backout threshold and backout queue attributes of the input queue.
第一类的示例是MQSC命令和一些SYSTEM对象，后者比如队列管理器在第一次启动时定义的各种system队列。
Examples of the first category are the MQSC commands, as well as SYSTEM objects such as the various SYSTEM queues that the queue manager defines the first time it starts up.
内部SCAMDB将在该队列上进行侦听，然后，在调用可选配置数据绑定类之后将消息提供给关联的SCA组件。
This is the queue over which the internal SCA MDB would listen on and then deliver messages to the associated SCA component after the optionally configured Data Binding class is invoked.
队列类的构造函数和析构函数负责创建和销毁互斥锁，见清单1。
The constructor and destructor of the queue class are responsible for the creation and destruction of the mutex, as shown in Listing 1.
通道启动程序的用户ID对保护队列及其上下文的MQQUEUE和mqadmin类的访问级别。
The level of access the channel initiator's user ID has to the MQQUEUE and MQADMIN class profiles that protect queues and their context.
在带宽的类(band width)中使用queue -limit命令设置不同的队列方法。
Varies with queueing method. Use the queue-limit command with a bandwidth class.
MQCON n类中的配置文件控制哪些userids有权连接队列管理器。
The profiles in the MQCONN class control which userids have authorization to connect to the queue manager.
代理队列管理器和这些应用程序的配置有三类
There are three possible configurations with the broker queue manager and these applications
在这个类的run方法中，从队列中的各个线程获取web页面、文本块，然后使用BeautifulSoup处理这个文本块。
In the run method of this class, grab the Web page, chunk, from off of the queue in each thread, and then process this chunk with Beautiful Soup.
电子邮件处理程序使用mailouts类检索未处理的电子邮件，然后再次使用它从队列中删除未处理的电子邮件。
The e-mail processor uses the mailouts class to retrieve the pending e-mail, then uses it again to delete the pending messages from the queue.
应用推荐