Lines Matching refs:reply
60 receives a blob (the reply), and the server receives the request and then
61 transmits the reply.
127 which the service receives; then the service transmits the reply data
155 (*) Reception of a reply data packet implicitly hard-ACK's all the data
158 (*) An call is complete when the request has been sent, the reply has been
159 received and the final hard-ACK on the last packet of the reply has
213 followed by the reply being received with one or more recvmsgs.
236 the reply is transmitted with one or more sendmsgs, and then the final ACK
549 (6) The reply data will then be posted to the server socket for recvmsg() to
550 pick up. MSG_MORE will be flagged by recvmsg() if there's more reply data
637 (8) The reply data should then be posted to the server socket using a series
655 (10) Up to the point the final packet of reply data is sent, the call can be
740 reply part of a server call. msg.msg_iovlen and msg.msg_iov specify the
846 The data message will be part of the reply on a client call and the