Alexander Khukhlaev

Another thing about delegates is that they are called in parallel, not sequentially. For example, if you pass the current time through a delegate and display it during processing, you...

But there is also the opposite situation with chat: for example, a server sends messages "Hello" and "world" almost simultaneously. And they can arrive at the client as "world Hello"

As for the main issue, I'll try to reduce my project to a minimal test. Something is hidden either in my code or in the code of this project.

> But there is also the opposite situation with chat: for example, a server sends messages "Hello" and "world" almost simultaneously. And they can arrive at the client as "world...

> We can however make some kind of an extension point for the event dispatcher. An option to supply your custom strategy of sending events sequentially. I think this will...

I seem to have found why there is a deadlock when using WatsonTCP. The situation is as follows: The server calls delegates continuously, while the client processes them (that is,...

Yes, it happens on localhost. I think it may reproduced with delegate invocation in infinite cycle: ```cs while (_stoped) { //Task.Delay(timeout); FireEvent(); } ``` Also we need method for start...

> Yes, it happens on localhost. I think it may reproduced with delegate invocation in infinite cycle: > > while (_stoped) > { > //Task.Delay(timeout); > FireEvent(); > } >...

And I finally managed to do a minimal reproducible test. This is the test itself. It should be located in RpcTests.cs. ```cs [Fact] public async Task Events_should_be_stopped() { using var...