1. 16 Jun, 2017 1 commit
  2. 09 May, 2017 2 commits
  3. 07 May, 2017 1 commit
  4. 05 May, 2017 5 commits
  5. 02 May, 2017 1 commit
  6. 01 May, 2017 1 commit
  7. 27 Apr, 2017 2 commits
  8. 26 Apr, 2017 3 commits
  9. 21 Apr, 2017 4 commits
  10. 20 Apr, 2017 1 commit
  11. 19 Apr, 2017 1 commit
    • Dominik Charousset's avatar
      Enable actors to receive streams as response · ce7a5a50
      Dominik Charousset authored
      This patch is only one half of enabling actors to "request" streams from
      others. Response IDs are currently not accounted for. This requires to
      somehow signalize the *intent* of setting a message ID. The current use
      case for this is starting a stream and then receiving the result.
      However, when attaching oneself to a stream as sink and wanting to
      provide the sink event handlers via response handler (e.g. via .then)
      then actors in the pipeline need to be able to figure out which of the
      two options is true.
      ce7a5a50
  12. 17 Apr, 2017 2 commits
  13. 16 Apr, 2017 10 commits
  14. 15 Apr, 2017 2 commits
  15. 13 Apr, 2017 2 commits
  16. 12 Apr, 2017 2 commits