SEND
Click on the red underlined text to get to the source
... TCP
to OPEN or CLOSE a connection, to SEND or RECEIVE data, or to obtain
STATUS about a connection. These calls are like other calls from user
...
... connection may be thought of as a stream of
octets. The sending user indicates in each SEND call whether the data
in that call (and any preceeding calls) should be immediately pushed
through to the receiving ...
... boundaries. The data in any particular segment may be the result of a
single SEND call, in whole or part, or of multiple SEND calls.
...
... segment may be the result of a
single SEND call, in whole or part, or of multiple SEND calls.
...
... TCP connection progresses from one state to another in response to
events. The events are the user calls, OPEN, SEND, RECEIVE, CLOSE,
ABORT, and STATUS; the incoming segments, particularly those
...
... point. As a result, A will probably try to OPEN the connection again
or try to SEND on the connection it believes open. In the latter
case, it receives the error message ...
... single calls. In particular, some implementations may wish to
automatically OPEN a connection on the first SEND or RECEIVE
issued by the user for a given connection ...
... connection. If the connection has
not been opened, the SEND is considered an error. Some
implementations may allow users to SEND first; in which case, an
...
... not been opened, the SEND is considered an error. Some
implementations may allow users to SEND first; in which case, an
automatic OPEN would be done. If the calling process is not
authorized to use this connection ...
... socket. Users who make use of OPEN with an unspecified
foreign socket can make use of SEND without ever explicitly
knowing the foreign socket address ...
...
However, if a SEND is attempted before the foreign socket
becomes specified, an error will be returned. Users can use the
...
...
In the simplest implementation, SEND would not return control to
the sending process until either the transmission was complete
or the timeout had been exceeded. However, this simple method ...
... asynchronous user interface in
which a SEND later elicits some kind of SIGNAL or
pseudo-interrupt from the serving TCP ...
... buffer address to be returned along with the coded response to
the SEND request. TCP-to-user signals are discussed below,
indicating the information which should be returned to the
...
... retransmitted), as flow control permits, until all have been
serviced. Thus, it should be acceptable to make several SEND
calls, followed by a CLOSE, and expect all the data to be sent
to the destination ...
... connection.
Depending on the implementation, users may receive abort
indications for each outstanding SEND or RECEIVE, or may simply
receive an ABORT-acknowledgment.
...
... an error message. In other cases there will be information
relating to the completion of processing a SEND or RECEIVE or
other user call.
...
...
OPEN
SEND
RECEIVE
CLOSE
...
... If the RST bit is set then, any outstanding RECEIVEs and SEND
should receive "reset" responses. All segment queues ...
... security/compartment and precedence in the TCB
then send a reset, any outstanding RECEIVEs and SEND should
receive "reset" responses. All segment queues ...
... If the SYN is in the window it is an error, send a reset, any
outstanding RECEIVEs and SEND should receive "reset" responses,
all segment queues ...
... positive acknowledgments for buffers which have been SENT and
fully acknowledged (i.e., SEND buffer should be returned with
"ok" response). If the ACK ...