1. 23 Aug, 2018 2 commits
  2. 22 Aug, 2018 3 commits
  3. 19 Aug, 2018 1 commit
  4. 18 Aug, 2018 1 commit
  5. 02 Aug, 2018 2 commits
  6. 09 Jun, 2018 4 commits
  7. 05 Jun, 2018 1 commit
  8. 03 Jun, 2018 2 commits
  9. 31 May, 2018 2 commits
    • Piotr Sikora's avatar
      Fix handling of SETTINGS_MAX_CONCURRENT_STREAMS. · 2ba13899
      Piotr Sikora authored
      The maximum number of outgoing concurrent streams is initially
      limited to 100 to avoid issues when the local endpoint submits
      lots of requests before receiving initial SETTINGS frame from
      the remote endpoint, since sending them at once to the remote
      endpoint could lead to rejection of some of the requests.
      
      This initial limit is overwritten with the value advertised in
      SETTINGS_MAX_CONCURRENT_STREAMS setting by the remote endpoint,
      but previously, it wasn't lifted if the remote endpoint didn't
      advertise that setting (implying no limits), in which case the
      limit of 100 was retained, even though it was never advertised
      by the remote endpoint.
      Signed-off-by: default avatarPiotr Sikora <piotrsikora@google.com>
      2ba13899
    • Piotr Sikora's avatar
  10. 12 May, 2018 5 commits
  11. 08 May, 2018 4 commits
  12. 07 May, 2018 1 commit
  13. 04 May, 2018 1 commit
  14. 03 May, 2018 2 commits
  15. 27 Apr, 2018 2 commits
  16. 22 Apr, 2018 2 commits
  17. 14 Apr, 2018 5 commits