Dispose and DataReceiver Task race condition in WatsonTcpClient

[fisherman6v6]

Hi Joel,

I noticed that sometimes inside the DataReceiver function even if a null check on _Client is performed, an ArgumentNullException is thrown by BuildFromStream. This is probably due to Dispose called in between the DataReceiver Check-for-Connection and the subsequent functions call. The exception won't cause major troubles since it gets caught in the last catch but I was wondering if this behavior is expected, or something can be improved.

Just a quick overview of my use case where I noticed this behavior. I developed a sort of distributed Event Aggregator where actors can register to events and a daemon server will dispatch these various events in form of notifications to registered actors. So, the demon has an active WatsonTcpServer which receives register requests and notifications to be dispatched. It will dispatch these notifications to registered actors using a onetime WatsonTcpClient that will be disposed just after the notification has been sent. This seems to cause the race condition mentioned above.

Thanks