DeviceTransaction.WaitForCompletionOrTimeout() can time out too soon when called from a client application

[Tim Long]

The timeout for a transaction should run from the moment it's command is sent, not from when the client app calls WaitForCompletionOrTimeout().

The transaction observer calls this method internally and will produce the correct result. The client app can also call the method but then may receive a timeout before the transaction even reaches the front of the queue. This can result in the application receiving timeouts for transactions that then go on to succeed. The effect can be particularly problematic with protocols that have transactions with long response times.

Originally created at 27/01/2017 21:19:19 by Tim Long as a bug with severity major.

[Tim Long]

Edited description

[Tim Long]

Fixed in 0.3.0

[Tim Long]

Edited description