Christopher Faulet 9d810cae11 BUG/MEDIUM: stream: Save unprocessed events for a stream ... A stream can be awakened for different reasons. During its processing, it can be early stopped if no buffer is available. In this situation, the reason why the stream was awakened is lost, because we rely on the task state, which is reset after each processing loop. In many cases, that's not a big deal. But it can be useful to accumulate the task states if the stream processing is interrupted, especially if some filters need to be called. To be clearer, here is an simple example: 1) A stream is awakened with the reason TASK_WOKEN_MSG. 2) Because no buffer is available, the processing is interrupted, the stream is back to sleep. And the task state is reset. 3) Some buffers become available, so the stream is awakened with the reason TASK_WOKEN_RES. At this step, the previous reason (TASK_WOKEN_MSG) is lost. Now, the task states are saved for a stream and reset only when the stream processing is not interrupted. The correspoing bitfield represents the pending events for a stream. And we use this one instead of the task state during the stream processing. Note that TASK_WOKEN_TIMER and TASK_WOKEN_RES are always removed because these events are always handled during the stream processing. [wt: backport to 1.7 and 1.6]		2016-12-12 19:10:58 +01:00
..
common	REORG: cli: move dump_text(), dump_text_line(), and dump_binary() to standard.c	2016-11-24 16:59:27 +01:00
import	CLEANUP: wurfl: reduce exposure in the rest of the code	2016-11-08 18:47:25 +01:00
proto	MINOR: task: Rename run_queue and run_queue_cur counters	2016-12-12 19:10:54 +01:00
types	BUG/MEDIUM: stream: Save unprocessed events for a stream	2016-12-12 19:10:58 +01:00