The server responds with an INIT-ACK, which includes the cookie (a unique context identifying this proposed connection).
服务器使用一个INIT - ACK报文进行响应，其中就包括了cookie(标识这个连接的惟一上下文)。
Guarantee levels: Tribes supports 3 levels of message delivery guarantee (NO_ACK, ACK, and SYNC_ACK).
有保证的消息传递：保证级别：Tribes支持3个级别的消息传递保证(NO_ACK、ACK和SYNC_ACK)。
If the client successfully receives this acknowledgement, the client completes the handshake with an ack acknowledgement.
如果客户机成功地收到这个确认，就通过发送ack确认完成握手。
In normal operation, the remote client responds with an ack packet that moves the half-open connection to fully open.
在正常操作中，远程客户机用一个ACK数据包进行响应，这会使半开的连接转换为全开的。
When the destination formulates its response, it includes an additional SOAP header (the ACK) in the message.
当目的地阐明其响应时，它在消息中包含一个附加的SOAP消息头 (ACK)。
A typical ack from this client does contain a SACK option for data higher than has been seen before, but it also contains sequence references to the immediately prior packets as well.
来自此客户机的典型应答包括一个SACK选项，它指向比前面出现的数据更高的数据，但它也包含指向前一个相邻包的序列。
As mentioned earlier, the sending side must agree to continually resend a message until it receives an ACK for that message.
正如前面提及的那样，发送端必须同意持续重新发送消息直到它收到该消息的ACK。
The client has a configurable option to add the SACK information relating to the most recently arrived data onto each ACK as it is transmitted.
客户机有一个可配置选项，在每个应答传输前，把与最近到达的数据相关的SACK信息增加到每个应答上。
Custom, with SACK: the last data set was gathered using the large window-inducing client while also including four SACK options on every ACK sent.
定制，启用SACK：最后的数据集使用了引入大窗口的客户机，同时也在每次发送ack时增加四个SACK选项。
Likewise, the receiving side must not only agree to send back an ack once they receive a message, but they must ignore any duplicate messages.
同样，接收方不仅要同意一旦收到消息，立刻返回一个ack，还必须忽略任何重复的消息。
If we received the response from the second UAS, we need to send an ACK to the first UAS.
如果我们接收了来自第二个UAS的响应，则需要将ACK发送到第一个UAS。
The server will acknowledge this by returning a packet with the ack flag set.
服务器将通过返回设置了ACK标志的包进行确认。
This ACK indicates that all messages have been received.
ACK表明所有的消息都已经收到了。
In response, the scanned host returns a packet with the SYN and ack flags set if the port is open.
如果该端口是打开的，则被扫描主机返回设置了syn和ack标志的包进行响应。
When a new TCP connection comes in from a client by means of a packet with the SYN bit set, the server creates an entry for the half-open connection and responds with a SYN-ACK packet.
当从客户机发来新的TCP连接时，数据包设置了SY n位，服务器就为这个半开的连接创建一个条目，并用一个SYN - ACK数据包进行响应。
If the port is not open, the scanned host sends a packet with the RST and ack flags set.
如果端口未打开，则被扫描主机发送设置了rst和ack标志的包。
Ack: Indicates that the acknowledgment number field is significant.
ACK：表明确认号字段是有意义的。
Finally, the client confirms this by sending a TCP packet back to the server with the ack flag set.
最后，客户机通过向服务器发送设置了ACK标志的tcp包进行确认。
The ACK request needs to be configured just like the INVITE request created previously.
ACK请求需要像前面创建的INVITE请求那样配置好。
The client selects the value of its SACK options whenever transmitting a delayed ACK.
在传输延迟的应答时客户机选择SACK选项的值。
For the non-SACK test cases, I used the typical length of the delayed ACK queue reported by the client as an approximation of the lower bound of the sender's window size.
对于非sack测试用例，我使用客户机报告的延迟应答队列的典型长度作为发送方窗口大小的近似值。
A SACK receiver, on the other hand, can issue an ack for 1 plus a SACK option for packets 3 through 9.
另一方面，SACK接收方可以发出包1的ACK和包3到包9的SACK选项。
The server answers with a packet where both the SYN and ACK flags are set.
服务器以设置了 SYN和ACK 标志的包应答。
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.
并且最后，一收到Message2，目的地就可以发送回最终的ACK来标志它收到了这个队列中的所有三个消息。
First is the definition of this Acknowledgment or ack; both SOAP stacks must understand what an ack is: what it looks like, what it means, and how to send it.
首先是Acknowledgment或者ack的定义；两个soap堆栈都必须理解ack是什么：其像什么，它意味着什么，以及如何发送它。
An attack called the SYN flood ensures that the ack packet never returns so that the server runs out of room to process incoming connections.
有一种称为syn泛滥(SYN flood)的网络攻击，它使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，这是发送方意识到它仅仅需要重新发送Message2。
Ack-Requested: This element lets the client determine whether an acknowledgement should be returned for a message sent.
Ack - Requested：这一元素允许客户端来决定对于发送的消息是否需要确认。
For one-way messages, the destination soap stack needs to generate a new soap envelope (with an empty soapenv: Body) in order to add this ack header.
对于单向消息，目的地soap堆栈需要生成一个新的soap信封(包含一个空的soapenv：Body)来添加这个ACK标签。
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，发送方就重新发送Message2且最终获得一个ack，如下面的清单4所示。
应用推荐