The MessageStatus is always Removed [IT is NOT a Bug]

[ghost]

Hello! It is amazing this library.

But, I had a problem with the reason parameter for the disconnection. When I pass MessageStatus different from 'Removed' to 'DisconnectClient' method, my delegate Disconnect method is called and the e.reason ever is MessageStatus.Removed. I tested directly in WatsonTcp Code and noticed that is a bug.
I didn't find a solution yet, I realized the bug now.

Thanks a lot!!

[jchristn]

Hi @StephesonAlves thanks for your kind words - what version are you using? I just tested on the latest (4.8.5) after amending the Test.Server project (to be able to pass in the reason) and it seems to work.

Here's an example of calling it with MessageStatus.Shutdown.

Here is the commit that includes the change to Test.Server: 60e3c88

[ghost]

I'm sorry!
Now I understand the situation.
In truth, I tried to do a kick the client from the Watson server with a specific reason and needed to catch this disconnection reason of the client yet in the server disconnect method by 'DisconnectionEventArgs.reason' to write in the server console log. I saw that this disconnection reason from the server is sent to the client and isn't the same in the server. I thought it was, but now I understand the real reason. It makes sense!!
IT is NOT a Bug! 👍

I solved my problem by creating a property that saves the client status.

Thanks a lot, man!

[jchristn]

Glad it's working for you! Cheers, Joel