Lines Matching refs:we

4 In this tutorial, we are going to write a very primitive HTTP/2
23 application protocol over TLS. In this tutorial, we use the
44 we have to instruct OpenSSL SSL_CTX to use ALPN, which we'll talk
70 Here we see ``SSL_CTX_get_alpn_protos()`` function call.  We instructs
71 OpenSSL to notify the server that we support h2, ALPN identifier for
190 Here we validate that HTTP/2 is negotiated, and if not, drop
194 events, we just simply tear down the connection.
197 handshake has completed successfully. After this we're ready to begin
230 Since we are creating a client, we use `nghttp2_session_client_new()`
258 Here we specify SETTINGS_MAX_CONCURRENT_STREAMS as 100. This is not
260 SETTINGS frame. To queue the SETTINGS frame for transmission, we call
267 After the transmission of the client connection header, we enqueue the
295 HTTP request, we call `nghttp2_submit_request()`. The ``stream_data``
329 In this function we feed all unprocessed, received data to the nghttp2
333 there may be pending frames for transmission, we call immediately
361 Since we use bufferevent to abstract network I/O, we just write the
363 continues to write all frames queued so far. If we were writing the
365 call, we'd soon receive an ``EAGAIN`` or ``EWOULDBLOCK`` error, since
370 memory consumption. In this example client however we don't implement
386 As described earlier, we just write off all data in `send_callback()`,
387 so there is no data to write in this function. All we have to do is
394 required and can be closed. Since we're using bufferevent and its
397 situation, we also check whether the output buffer is empty or not. If
398 all of these conditions are met, then we drop the connection.
425 In this tutorial, we just print the name/value pairs on stderr.
447 In this tutorial, we are just interested in the HTTP response HEADERS
468 stream ID, we just write the received data to stdout. Note the output
492 If the stream ID matches the one we initiated, it means that its
493 stream is going to be closed. Since we have finished receiving
494 resource we wanted (or the stream was reset by RST_STREAM from the
495 remote peer), we call `nghttp2_session_terminate_session()` to