walkero
/
nghttp2
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Update doc

This commit is contained in:
Tatsuhiro Tsujikawa 2013-12-26 00:23:43 +09:00
parent 9cb8754d09
commit 67b265f737
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/tutorial-client.rst
View File

@ -443,7 +443,7 @@ is about to close::
if(session_data->stream_data->stream_id == stream_id) { if(session_data->stream_data->stream_id == stream_id) {
fprintf(stderr, "Stream %d closed with error_code=%d\n", fprintf(stderr, "Stream %d closed with error_code=%d\n",
stream_id, error_code); stream_id, error_code);
rv = nghttp2_session_fail_session(session, NGHTTP2_NO_ERROR); rv = nghttp2_session_terminate_session(session, NGHTTP2_NO_ERROR);
if(rv != 0) { if(rv != 0) {
return NGHTTP2_ERR_CALLBACK_FAILURE; return NGHTTP2_ERR_CALLBACK_FAILURE;
} }
@ -454,9 +454,10 @@ is about to close::
If the stream ID matches the one we initiated, it means that its If the stream ID matches the one we initiated, it means that its
stream is going to be closed. Since we have finished to get the stream is going to be closed. Since we have finished to get the
resource we want (or the stream was reset by RST_STREAM from the resource we want (or the stream was reset by RST_STREAM from the
remote peer), we call `nghttp2_session_fail_session()` to commencing remote peer), we call `nghttp2_session_terminate_session()` to
the closure of the HTTP/2.0 session gracefully. If you have some data commencing the closure of the HTTP/2.0 session gracefully. If you have
associated for the stream to be closed, you may delete it here. some data associated for the stream to be closed, you may delete it
here.
libevent-client.c libevent-client.c
----------------- -----------------