Hi all,

Today I stumbled over something when I was testing re-connect behavior when 
re-using PlcReadRequests over a connection (Like using the connection-cache). 
This seems to work fine as long as the initial connection is still available. I 
think I wouldn’t even need to get the connection to execute the repeated read 
operation. This also could result in concurrent execution of requests.

I think possibly passing in the connection to the execute method and using that 
to execute the operation would be an option. We would need to save the 
connection string for which a request was built and then check this on every 
execution.

The more I think of it the more problematic do I think this issue is.

However it would be quite a big breaking change :-(

Chris

Reply via email to