[Crepestrom]

No description provided.

[Wunka]

This is not the right idea. The threadcontext helps us, so that we don't change data from 2 different threads. Just setting it to something different completly breaks our assumption of what the threadContext is.

[Crepestrom]

This is not the right idea. The threadcontext helps us, so that we don't change data from 2 different threads. Just setting it to something different completly breaks our assumption of what the threadContext is.

what do you mean
its client receive
its being received by the client
why cant it be set?

[Wunka]

Setting it destroys all our assumptions about that every function which has a threadContext assert at the start is run on the same thread. This makes all variables that are handled in these functions vulnerable to data races.

It's not about if its a clientReceive function. Its about which thread it runs on. And the threadContext tells you that.