Zhenyu Guo

@shengofsun I cannot reproduce this on my machine. Is it because the async-read/write ops may throw exceptions when the other threads call socket::close() concurrently, which leads to the coredump as...

I'm re-running the test with more tracing options now.

the fix is still incomplete - the client may have different versions of code compared to the servers, in which case we need to have all task code transmitted as...

@qinzuoyan this case is a little bit different compared to error code. Currently for the case of replicated read/write, the task code is embedded as part of the msg body...

I'm doing this now.

add some examples in https://github.com/imzhenyu/rDSN/pull/103 @glglwty please add more when you do the profiling on demand.