1. 13 4月, 2016 1 次提交
  2. 07 4月, 2016 1 次提交
  3. 06 4月, 2016 1 次提交
  4. 04 4月, 2016 1 次提交
  5. 03 4月, 2016 3 次提交
  6. 23 3月, 2016 1 次提交
  7. 21 3月, 2016 1 次提交
  8. 19 3月, 2016 1 次提交
  9. 18 3月, 2016 1 次提交
  10. 14 3月, 2016 1 次提交
  11. 13 3月, 2016 1 次提交
  12. 10 3月, 2016 1 次提交
  13. 09 3月, 2016 8 次提交
  14. 08 3月, 2016 9 次提交
  15. 07 3月, 2016 5 次提交
  16. 01 3月, 2016 1 次提交
  17. 29 2月, 2016 2 次提交
    • M
      Refactor the async wait fd logic · ff75a257
      Matt Caswell 提交于
      Implementation experience has shown that the original plan for async wait
      fds was too simplistic. Originally the async logic created a pipe internally
      and user/engine code could then get access to it via API calls. It is more
      flexible if the engine is able to create its own fd and provide it to the
      async code.
      
      Another issue is that there can be a lot of churn in the fd value within
      the context of (say) a single SSL connection leading to continually adding
      and removing fds from (say) epoll. It is better if we can provide some
      stability of the fd value across a whole SSL connection. This is
      problematic because an engine has no concept of an SSL connection.
      
      This commit refactors things to introduce an ASYNC_WAIT_CTX which acts as a
      proxy for an SSL connection down at the engine layer.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      ff75a257
    • R
      0421c00e
  18. 27 2月, 2016 1 次提交