缺省情况下，日志记录消息被发送到控制台。
事务性消息被发送到非事务性队列中。
A transactional message is sent to a non-transactional queue.
未加密的消息被发送到仅接受加密消息的队列中。
An unencrypted message is sent to a queue that accepts only encrypted messages.
SOAP响应消息被发送到服务请求者，表明服务已经完成，并返回结果。
A SOAP response message is sent to the service requestor indicating that the service is completed, returns the result.
该消息被发送到的复选框的父控制，利用控制作为第四参数的手柄。
The message is sent to the parent control of the check box, using the handle of the control as the fourth parameter.
未经身份验证的消息被发送到仅接受经过身份验证的消息的队列中。
An unauthenticated message is sent to a queue that accepts only authenticated messages.
在场景1中，大量消息被发送到数据流并通过集群中的两个队列管理器进行处理。
In Scenario 1, a large number of messages are sent to the flow and processed by both queue managers in the cluster.
消息被发送到服务器目的地和域 （domain），而不是发送到物理地址。
Messages are sent to server destinations and domains rather than physical addresses.
与RMM 不同的是，RUDP 是一个 “点对点”协议：消息被发送到一个特定目标。
Unlike RMM, RUDP is a point-to-point protocol in which messages are sent to a specific destination.
DXLCreateD oc代理处理DXL文档中的XML数据，返回的消息被发送到客户机。
The XML data in the DXL document is processed by the DXLCreateDoc agent, and the return message is sent back to the client.
消息被发送到级别最高的一个或多个队列，因此这个细粒度允许对队列排序，以表明应用程序可用性的等级。
Messages are sent to the highest ranked queue or queues, and so this granularity allows queues to be ordered to indicate grades of application availability.
RPC是基于消息的：消息被发送到大的服务器，然后，在某一刻，会收到从大的服务器发出的“好，我做完了”的消息。
RPC is message-based: a message was sent to the big server, and, at some point, a message saying "OK, I'm done" will be received from that big server.
要在消息被发送到用户之前截取这些消息，必须指定一个扩展于 com.ibm.collaboration.realtime.messages.MessageHandlerPreCallback类的扩展点类。
To intercept messages before they are sent to the user, an extension point class must be specified that extends the com.ibm.collaboration.realtime.messages.MessageHandlerPreCallback class.
这个解决方案确保消息只被发送到拥有活动消息使用方应用程序的那些实例。
The solution ensures that messages are sent to only those instances that have active message consumer applications.
事实上，该消息将可能被发送到类，然后这将导致一个已创建对象的返回值，所以与我说的有点不符。
Actually, this message would likely be sent to the class that would then result in a return value of the created object, so I cheated a bit.
这意味着，如果请求中介流中的请求消息在其消息头中包含一个地址，则请求消息将被发送到位于该地址的提供程序。
This means that, if the request message in the request mediation flow contains an address in the message header, the request message is sent to the provider at that address.
它同样也为作为SOAP消息(它被发送到Web服务端点)中消息信息头的这个信息的表示定义了一组规则。
It also defines a set of rules for the represention of this information as message information headers in SOAP messages that are sent to Web services endpoints.
最后，绑定和验证之后，HIPAA271消息通过EDIGateway被发送到请求的客户。
Finally, after bundling and validation, the HIPAA271 message is sent to the requesting client through the EDI Gateway.
因此，由连接到QM1 的应用程序放置的消息将不会被发送到QM2，这样，所有消息都将被发送到QM3。
Therefore messages put by the application connected to QM1 will not be sent to QM2, and hence, all messages will be sent to QM3.
此消息随后被发送到队列，一个包含相关ID的刷新响应已经组装完毕并被发送到客户端。
The message is then sent to the queue and a Refresh Response containing the correlation ID is prepared and returned to the client.
使用xmlt节点时，请注意消息树将首先被序列化，然后再被发送到转换引擎。
When using XMLT nodes, be aware that the message tree is first serialized and then sent to transformation engine.
“消息”是带类型的数据对象的集合，它们只能被发送到端口，而不能指定发送到具体的任务或线程。
"Messages" are collections of typed data objects, they can only be sent to ports - not specific tasks or threads.
在Linux引导进程中，大量消息将被发送到控制台，描述正在引导的内核、系统硬件、以及其他内核相关事项。
During the Linux boot process, a large number of messages are emitted to the console, describing the kernel being booted, the hardware of your system, and other things related to the kernel.
(初始化)消息是不是首先被发送到类的消息，甚至比调用类方法更早？
Is it true that the "initialize" message is sent to a class before any other messages, even class methods calls?
一旦事务性消息传递失败，则在所有否定的和不确定的情况下，消息将被发送到源计算机上的事务性死信队列。
In the case of delivery failure for transactional messages, the message is sent to the transactional dead-letter queue on the source computer in all negative and in-doubt cases.
一旦事务性消息传递失败，则在所有否定的和不确定的情况下，消息将被发送到源计算机上的事务性死信队列。
In the case of delivery failure for transactional messages, the message is sent to the transactional dead-letter queue on the source computer in all negative and in-doubt cases.
应用推荐