Oct 9, 2014 at 7:55 PM
Edited Oct 9, 2014 at 8:02 PM
Using revision 42563, TcpDuplexServerProtocolSetup and TcpDuplexClientProtocolSetup.
I have 3 different events: PassStarted, Information, ApStateChanged. PassStarted event have some byte array in args (~40kb).
On server I fire events in order one after another without pauses:
On client I received events in different order:
- PassStarted (most "heavy" event)
So I have not ordered event handlers invocations. Is this behavior really correct, or Zyan or I have a bug?
If this is correct behavior - how can I make invocations ordered?