- 02 Jan, 2015 13 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
Benchmark shows 10% faster with libev compared to libevent. Also response time in high load condition is much faster.
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
-
Tatsuhiro Tsujikawa authored
-
- 31 Dec, 2014 1 commit
-
-
Alexis La Goutte authored
and it is now valided by http://lint.travis-ci.org/ (Hooray, your .travis.yml seems to be solid!)
-
- 30 Dec, 2014 1 commit
-
-
Alexis La Goutte authored
-
- 24 Dec, 2014 1 commit
-
-
Tatsuhiro Tsujikawa authored
-
- 23 Dec, 2014 7 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 22 Dec, 2014 2 commits
-
-
Tatsuhiro Tsujikawa authored
-
-
- 21 Dec, 2014 3 commits
-
-
Kazuho Oku authored
-
Kazuho Oku authored
-
Kazuho Oku authored
-
- 20 Dec, 2014 4 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
Initially, we use nghttp2_stream.data_item to refer only item with DATA frame. But recently we use it to refer HEADERS frame as well. So it is better to call just item rather than data_item. This applies to all related functions.
-
- 19 Dec, 2014 3 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 18 Dec, 2014 2 commits
-
-
Tatsuhiro Tsujikawa authored
Previously session_after_frame_sent is called after we detected all data is sent. In nghttp2_session_mem_send, we only detect it in the next call of the function. It means that if a frame data bearing END_STREAM is on flight to the peer as a result of nghttp2_session_mem_send, peer may get that data and knows the stream closure and issues new stream. We may receive this new stream before the next nghttp2_session_mem_send call, which means that we may incorrectly assumes that peer violates maximum concurrent stream limit. To fix this issue, we separate session_after_frame_sent into 2 functions: session_after_frame_sent1 and session_after_frame_sent2. session_after_frame_sent1 handles on_frame_send_callback and stream closure and we call this early in nghttp2_session_mem_send. This makes number of streams are synchronized correctly with peer.
-
Tatsuhiro Tsujikawa authored
-
- 17 Dec, 2014 2 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 16 Dec, 2014 1 commit
-
-
Alexis La Goutte authored
-