时间：2018年10月18日(星期四) 17:47
> 收件人：Zhijiang(wangzhijiang999)
> 抄 送：Nico Kruber ; dev
> 主 题：Re: [DISCUSS] Improve broadcast serialization
>
> Hey,
>
> I also think that 3rd option is the most promising, however logic of “dirty”
> channels might be causing some overheads.
hird point
> from current thoughting, which keeps the same behavior like normal "emit"
> mixing with "broadcastEvent".
>
> Best,
> Zhijiang
> --
> 发件人：Piotr Nowojski
> 发送时间：2018年10月17日(星期三) 19:
2.2. The 2.1 is your
> proposal[c] which has no problem for mixed write mode, so no need additional
> flush. The 2.2 is just as your proposal[2] which concerns additional flush.
> Maybe my last reply make you misunderstand.
>
> I can submit jira for above 2.1 first if no othe
help review PR if have
> time. :)
>
Sure :)
Piotrek
>
> Best,
>
> Zhijiang
> --
> 发件人：Piotr Nowojski
> 发送时间：2018年7月18日(星期三) 16:37
> 收件人：dev ; Zhijiang(wangzhijiang999)
>
> 主 题：Re: [DISCUSS] Improve broadcast serializ
gt; Zhijiang
>
>
> ------------------
> 发件人：Piotr Nowojski
> 发送时间：2018年7月17日(星期二) 23:31
> 收件人：dev ; Zhijiang(wangzhijiang999)
>
> 主 题：Re: [DISCUSS] Improve broadcast serialization
>
> Hi
>
> Generally speaking t
Hi
Generally speaking this would be a nice optimisation, however it might be
tricky to implement. The thing to keep in mind is that currently interface
allow to interleave broadcasting and normal sending, because of that at any
given time some serialisers can have more data then others. For exa
