> It's also quite natural, i think, to want to use multiple separate streams. i dont think i'd call it natural per se - i'd say it's just "easy" to do so, and

> It's also quite natural, i think, to want to use multiple separate streams. i dont think i'd call it natural per se - i'd say it's just "easy" to do so, and especially if each of these separate streams are managed by different teams, and it makes business sense to separate the responsibility. There should be a framework, perhaps, to allow "multiplexing" of multiple streams of events into one actual tcp connection. Of course, this requires some work, but i dont think it's actually that much extra work. It just needed to be planned out as a need, as it might be a tad hard to tack it on after the fact (tho that's not impossible either).