1. 04 5月, 2019 2 次提交
  2. 03 5月, 2019 3 次提交
  3. 02 5月, 2019 1 次提交
  4. 01 5月, 2019 1 次提交
  5. 27 4月, 2019 4 次提交
  6. 26 4月, 2019 3 次提交
  7. 24 4月, 2019 1 次提交
  8. 21 4月, 2019 1 次提交
  9. 18 4月, 2019 2 次提交
  10. 17 4月, 2019 1 次提交
    • R
      LeakAwareDataBuffer related fixes · 375090bb
      Rossen Stoyanchev 提交于
      Following on 3ebbfa21 where the local
      refCount was removed in favor of using the internal refCount of the
      native data buffer, this commit ensures that LeakAwareDataBufferFactory
      uses a PooledDataBufferFactory delegate by default.
      
      There are also fixes for test issues with eager allocation uncovered by
      these changes in StringDecoder and ResourceDecoder.
      375090bb
  11. 12 4月, 2019 4 次提交
  12. 11 4月, 2019 3 次提交
  13. 10 4月, 2019 1 次提交
  14. 09 4月, 2019 2 次提交
  15. 08 4月, 2019 3 次提交
  16. 06 4月, 2019 5 次提交
  17. 05 4月, 2019 1 次提交
    • S
      Add support for Coroutines Flow · a8d6ba99
      Sebastien Deleuze 提交于
      Flow is a Kotlin Coroutines related cold asynchronous
      stream of the data, that emits from zero to N (where N
      can be unbounded) values and completes normally or with
      an exception.
      
      It is conceptually the Coroutines equivalent of Flux with
      an extension oriented API design, easy custom operator
      capabilities and some suspending methods.
      
      This commit leverages Flow <-> Flux interoperability
      to support Flow on controller handler method parameters
      or return values, and also adds Flow based extensions to
      WebFlux.fn. It allows to reach a point when we can consider
      Spring Framework officially supports Coroutines even if some
      additional work remains to be done like adding
      interoperability between Reactor and Coroutines contexts.
      
      Flow is currently an experimental API that is expected to
      become final before Spring Framework 5.2 GA.
      
      Close gh-19975
      a8d6ba99
  18. 04 4月, 2019 2 次提交