What you have found is one possible way of having confirmation packets. Having said that this functionality is actually provided within the core feature set. You can enable this functionality on a global basis, per connection or per send basis by creating a new SendRecieveOptions list. The following forces a receive confirmation:
SendReceiveOptions newOptions = (SendReceiveOptions)NetworkComms.DefaultSendReceiveOptions.Clone();
newOptions.ReceiveConfirmationRequired = true;
Connection conn = TCPConnection.GetConnection(connectionInfo, newOptions);
try
{
conn.SendObject("Message", "this is a test message");
}
catch (ConfirmationTimeoutException)
{
//If the server does not send a recieve confirmation within the default timeout this exception will be thrown.
}
This is handled automatically by the receiving end so that you do not have to worry about it.
Regards,
Marc