3 ms·
Yes, although a key difference seems to be that steps in the pipeline are allowed to interfere with arbitrary other steps.
by wool_gather 7y ago
Yes, although a key difference seems to be that steps in the pipeline are allowed to interfere with arbitrary other steps.
- tabtab 7y agoTraditional event-driven programming often has event priority values or rank, and an optional "end event processing" operation associated with events, doesn't it? MS-Outlook's "rule engine" has these, for example. That seems the same thing as "allowed to interfere with arbitrary other steps". Sure, you can "lock out" using/modifying such operations, but one must know when and where to lock someone/something out. Programming is still a persnickety endeavor with or without using events.
- AstralStorm 7y agoAt least events themselves are processed sequentially, so having a trace of them is meaningful. Here, anything goes, as there's a multitude of queues.