1. 02 Jan, 2015 16 commits
  2. 31 Dec, 2014 1 commit
  3. 30 Dec, 2014 1 commit
  4. 24 Dec, 2014 1 commit
  5. 23 Dec, 2014 7 commits
  6. 22 Dec, 2014 2 commits
  7. 21 Dec, 2014 3 commits
  8. 20 Dec, 2014 4 commits
  9. 19 Dec, 2014 3 commits
  10. 18 Dec, 2014 2 commits
    • Tatsuhiro Tsujikawa's avatar
      nghttp2_session_mem_send: Handle stream closure early · 8bac2087
      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.
      8bac2087
    • Tatsuhiro Tsujikawa's avatar
      Fix memory leak · ce1bf11d
      Tatsuhiro Tsujikawa authored
      ce1bf11d