Ack! Same problem!

同样的问题又发生了！

This ACK indicates that all messages have been received.

ACK表明所有的消息都已经收到了。

Ack: Indicates that the acknowledgment number field is significant.

ACK：表明确认号字段是有意义的。

In our dearth of ack-ack guns all sorts of contrivances were used.

在缺少高射炮的时候，我们利用了各种各样的巧妙方法。

The server answers with a packet where both the SYN and ACK flags are set.

服务器以设置了 SYN 和 ACK 标志的包应答。

Finally, the client confirms receipt with an ack packet (see Figure 4).

最后，客户机使用一个ACK报文确认已接收到报文(请参见图4)。

The server will acknowledge this by returning a packet with the ack flag set.

服务器将通过返回设置了ACK标志的包进行确认。

The Buy Ack action you just created meets this requirement for the Buy event.

您刚才创建的Buy Ack操作满足Buy事件的这个要求。

Press the button to post the comment. Press button Ack also post the comment.

按钮发布备注，“确认”钮也会发布备注。

The tcp_input on the server side processes this ack packet and calls soisconnected .

服务器端上的tcp _ input处理此ack包，并调用soisconnected 。

If the port is not open, the scanned host sends a packet with the RST and ack flags set.

如果端口未打开，则被扫描主机发送设置了rst和ack标志的包。

Again, nothing too complicated. Now let's see what the destination's ACK looks like.

看，没什么太复杂的。

The client selects the value of its SACK options whenever transmitting a delayed ACK.

在传输延迟的应答时客户机选择SACK选项的值。

The ACK request needs to be configured just like the INVITE request created previously.

ACK请求需要像前面创建的INVITE请求那样配置好。

If we received the response from the second UAS, we need to send an ACK to the first UAS.

如果我们接收了来自第二个UAS的响应，则需要将ACK发送到第一个UAS。

Send an immediate ACK to the customer confirming the request and supplying a confirmation number.

向客户发送即时的ACK，确认请求并提供校验码。

The benefit of using UDP is that it is state less so there is no problem of managing ack info.

使用UDP的好处是，它区块少所以没有应答信息管理的问题。

UA1 acknowledges the 200 OK response by sending an ack request to UA2, where the call was forwarded.

UA 1通过向ua2发送一次ack请求，来确认响应200 OK。

In response, the scanned host returns a packet with the SYN and ack flags set if the port is open.

如果该端口是打开的，则被扫描主机返回设置了syn和ack标志的包进行响应。

Guarantee levels: Tribes supports 3 levels of message delivery guarantee (NO_ACK, ACK, and SYNC_ACK).

有保证的消息传递：保证级别：Tribes支持3个级别的消息传递保证(NO_ACK、ACK和SYNC_ACK)。

Finally, the client confirms this by sending a TCP packet back to the server with the ack flag set.

最后，客户机通过向服务器发送设置了ACK标志的tcp包进行确认。

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选项。

When the destination formulates its response, it includes an additional SOAP header (the ACK) in the message.

当目的地阐明其响应时，它在消息中包含一个附加的 SOAP 消息头 (ACK)。

In normal operation, the remote client responds with an ack packet that moves the half-open connection to fully open.

在正常操作中，远程客户机用一个ACK数据包进行响应，这会使半开的连接转换为全开的。

The server responds with an INIT-ACK, which includes the cookie (a unique context identifying this proposed connection).

服务器使用一个INIT - ACK报文进行响应，其中就包括了cookie(标识这个连接的惟一上下文)。

Ack-Requested: This element lets the client determine whether an acknowledgement should be returned for a message sent.

Ack - Requested：这一元素允许客户端来决定对于发送的消息是否需要确认。

If the client successfully receives this acknowledgement, the client completes the handshake with an ack acknowledgement.

如果客户机成功地收到这个确认，就通过发送ack确认完成握手。

As mentioned earlier, the sending side must agree to continually resend a message until it receives an ACK for that message.

正如前面提及的那样，发送端必须同意持续重新发送消息直到它收到该消息的ACK。

You can specify which incoming TCP packets to scan and discard those that don't match the flags ack, FIN, PSH, RST, SYN, or URG.

可以指定应该扫描哪些到达的TCP数据包，丢弃不与ack、FIN、P SH、RST、syn或urg标志匹配的数据包。

It sounds amusing, but not if you have a large green brain and go "Ack" a lot.Stay away or arm yourself with really top-level shielding.

这似乎有些好笑，但如果你有个经常运转的绿色大脑袋，那最好离远些或者用些真正高水平的保护罩将自己武装起来。