Any support coming for streaming applications?

[jessmorecroft]

Hi, I'm wondering if there are plans for streaming additions like those here: https://github.com/maikel/senders-io? This looks to have a concept of a fork sequence, which then allows accepting new connections while continuing to manage existing. Something like a flat map on a dynamic sequence, with a parallel parameter would be the generic equivalent. Anyway, I suspect a very long road to some of these features but I wondered if there were any plans / papers that might show what's to come?

[jessmorecroft]

Just a quick update for anyone interested.

As I have read tests/ examples and understood stdexec more I have noted that async_scope and spawn appear to be the primary means of handling a separate streams of incoming work and handling in parallel, with a final wait on the scope for all spawned operations to finish. For a single stream, the pattern is effectively read | process | repeat_until_effect().

What I may eventually investigate is a means of buffering between senders, effectively enabling pipelining / increasing bandwidth. This is something I saw was addressed by @kirkshoop in an old thread, where he suggested something like:

when_all( read(socket) | process | push(buffer) | repeat_effect_unit(), read(buffer) | process | push(buffer2) | repeat_effect_until(), read(buffer2) .... etc)

The missing piece here, at least in stdexec I believe, is the buffer impl.