Simplify chat example?

[rossberg]

My attempt to simplify the chat example a little bit. In particular, removes all "async ()", since it seemed to to have only been used to sequentialise where it wasn't really necessary. @crusso, am I missing something?

[crusso]

Well, you can construct it this way but I wanted a subscriber to know when all other subscribers had received his message. Otherwise he'll just post all his messages and exit which doesn't make for very good chat ;->

[crusso]

With the original semantics once could still try to parallelise the broadcast by creating a list of asyncs and then waiting for them all (Ideally in parallel, but we'd need to build that in I suspect)

[rossberg]

Isn't that an impractical architecture, though? One slow subscriber would stall the entire chat room. Message latency is generally high on our platform, so even under good conditions and with the parallelisation you describe, n-way synchronisation would likely make a real-time interactive app like this too laggy.

[crusso]

Sure, I was just pointing out that the semantics had changed. I never intended this to be a real world example ;->

[nomeata]

@rossberg, I think you can press the merge button.

[nomeata]

(I even did the merge from master for you :-))

[rossberg]

Thanks!