Zina: I'm leaving him a message 2 taped to my computer screen.
我要留张纸条给他，贴在我的电脑屏幕上。
So to complete the scenario, upon receipt of this ACK, the sender resends Message 2 and eventually gets an ACK, as shown in Listing 4 below.
因此完成这一场景，一收到这个ACK，发送方就重新发送Message 2且最终获得一个ack，如下面的清单4所示。
And finally, upon receipt of message 2, the destination can now send back one final ack indicating that it received all three messages for this sequence.
并且最后，一收到Message 2，目的地就可以发送回最终的ACK来标志它收到了这个队列中的所有三个消息。
After the first set of messages, notice how the destination sends back an ack indicating that it received messages 1 and 3 — the sender now knows that it needs to resend just message 2.
在首批消息以后，请注意目的地怎么发送回ack来标志它收到了Messages1和3，这是发送方意识到它仅仅需要重新发送Message 2。
Subsequently, at point (2), the user exit is invoked when the message is propagated to the node for processing.
随后在点 (2) 处，在消息传播到该节点进行处理时调用了用户出口。
However, in general when the two nodes are in separate message flows (for example, Figure 2), you need to forward the necessary correlation information to the reply flow yourself.
然而，在一般情况下，当两个节点在单独的消息流中时(例如，图2)，您需要自己将必要的相关性信息转发给应答流。
Notice that a dotted line guide shows you exactly where the message set will be dropped (see Figure 2).
注意一个带点的线将会向您显示消息集合的精确位置(如图2所示)。
A corresponding example message to illustrate how the configuration directs message creation is shown in Listing 2.
清单2中给出了一个相应的示例消息，演示了该配置如何指导消息的创建。
UDDI version 2 has modified some existing message APIs and changed the version identifier on all incoming and outgoing messages.
UDDI版本2修改了一些已有的消息api，并改变了所有进入和发出的消息上的版本标识符。
Listing 2 shows that each WSDL message has two WSDL parts and each part refers to a global element.
清单2显示每个WSDL消息有两个WSDL部分，每个部分引用一个全局元素。
This data is highlighted, in the sample XML transaction message below, which would represent step 4 in Figure 2.
下面的示例XML事务消息突出显示了该数据，它表示图2中的步骤4。
Figure 2 illustrates several common message formats — XML, tagged, fixed-length, and native.
图2显示了一些常见的消息格式——XML、带标记、定长、原生。
Once the connection is successful, you will get a message indicating success as shown in Figure 2.
连接一旦成功，您就会获得显示成功的消息，如图2所示。
Throughput scaling from 2 adapters/1 node to 4 adapters/2 nodes was computed for each send message size.
对于每种消息大小，分别计算从2 个适配器/1 个节点到4 个适配器/2 个节点的吞吐量变化。
Listing 2 shows the XML output message that is produced by the map.
清单2给出这个映射产生的XML输出消息。
Section 2 of the message flow extracts the schema from the WSDL document that is passed as part of the logical tree from the HTTP node.
消息流的第2部分从http节点作为逻辑树的一部分传递的WSDL文档提取模式。
Figure 4 shows the defaults of 5 MB for the total message size and 2 MB worth of NSD output, which is read starting from the beginning of the file, so it's the first 2 MB of the file that is used.
图4显示消息总大小的默认值是5MB,NSD输出是2 MB，因为NSD输出是从文件的开头开始读取的，所以它是文件的前2 MB。
Table 2 lists the properties of a message stereotype.
表二列出了一个消息原型的属性。
For example, a message published at QoS 2 to a subscriber that specified QoS 1 for that topic is delivered at QoS 1.
例如，以QoS2向订阅者发布的消息，若订阅者指定此主题的级别为QoS1，那么主题就会以QoS 1传递。
The output from Listing 2 shows a log message with a time stamp in uppercase
清单2的输出显示了一个大写的、带时间戳的日志消息
You see the SQL0440N error message from Listing 2 for object TEST.v2.
您会在清单 a 中看到 TEST.v2对象的SQL0440N错误消息。
The code in listing 2 publishes a message to indicate that Air Freedom's flight 1024 has arrived at London Heathrow Airport (LHR).
清单2中的代码发布的消息表明AirFreedom的1024次航班已经抵达伦敦希思罗机场(LHR)。
To implement this portlet, first define an interface to abstract the implementation details of the message store (Listing 2).
为了实现这个portlet，首先要定义一个接口以对消息存储器的实现细节进行抽象(清单2)。
Open test/reports/html/index.html in your Web browser to see the error message shown in Figure 2
在Web浏览器中打开test/reports/html/index.html，您将看到如图 2所示的错误消息。
Publish-and-subscribe messaging is a way to achieve one-to-many delivery semantics between applications for a given message as shown in figure 2.
发布-订阅消息传递是针对一条特定消息在应用程序间实现一对多传递语义的消息传递方式，如图2所示。
An instance of the ActiveMQ ra, to access the ActiveMQ message broker configured in Listing 2, using the TCP protocol for transport.
一个Active MQra实例，它使用TCP传输协议来访问清单2中所配置的Active MQ消息代理。
Subscribers can specify a maximum QoS for delivery of messages on a per-topic basis, so a message published at QoS 2 May not be delivered to its subscribers at that level.
订阅者可以基于每个主题指定消息传递的最大QoS，所以若消息在QoS2发布，此消息有可能不是在该级别发布给其订阅者。
Successful installation of the WSGW applications will result in the message shown in Listing 2 in the OS command shell (with an appropriate value for the servername parameter).
如果WSGW应用程序安装成功，在OScommandshell(带有适当的服务器名称参数值)中会显示如清单2所示的消息。
When you roll back the transaction in Listing 2, the message received is restored in the queue bookorder and the row will also be removed from shipping_tab.
当回滚清单2中的事务时，接收到的消息被恢复到队列bookorder中，这一行将从shipping _ tab中删除。
Figures 2 and 3 are snapshots of the output message data using rfhutil.
图2和3是使用rfhutil的输出消息的快照。
应用推荐