Lines Matching full:initiated

571 If no QUIC connection attempt was ever initiated using the given SSL object, the
573 connection closure process is initiated if it has not already begun.
735  * example, a remotely initiated unidirectional stream where
736  * SSL_get_stream_write_state is called, or a locally initiated unidirectional
861 locally initiated.
864 initiated by QUIC, and 0 if it was initiated by the application. The namespace
994  * QUIC: Returns 1 if the stream was locally initiated, or 0 otherwise.
1136  *     Remotely-initiated streams are placed in the accept queue for application
1143  *     peer opens a remotely-initiated stream, a locally-initiated bidirectional
1145  *     remotely-initiated stream before the local application calls `SSL_write`
1156  *     remotely-initiated stream, a unidirectional TX-only stream is created and
1158  *     If the peer creates a remotely-initiated stream prior to the first call
1536 Where connection closure is initiated remotely rather than locally, only the
1552 **Q. Can data be received on a locally initiated bidirectional stream before any
1577 >the sending part initiated by the endpoint (type 0 for a client, type 1 for
1585 order to receive data on a locally-initiated bidirectional stream before sending
1601 application would want to create a locally-initiated stream and then have the
1602 peer transmit on it first, rather than simply use a remotely-initiated stream.
1606 **Q. How should single-stream operation support locally and remotely-initiated
1610 it is initiated by the client or server. Therefore, in single stream operation,
1612 client-initiated or server-initiated stream initiation, and whether a
1618 receiving first on a locally initiated stream here, thus we avoid supporting
1622 before it calls `SSL_read` by definition is using a locally-initiated stream,
1623 and an application which does the opposite is using a remotely-initiated stream.
1627 Supporting locally-initiated streams (`SSL_write` called first) is simple;
1630 Supporting remotely-initiated streams (`SSL_read` called first) is a little
1632 initial call to `SSL_read` implying use of a remotely-initiated stream. However,
1633 this would mean we are creating state tracking a remotely-initiated stream
1640 Ergo, creation of a default remotely-initiated stream needs to be deferred
1652   - The local application calls `SSL_write()` (`len > 0`). A locally-initiated