PLCinterface classes write- and read-methods both swallows IOExceptions. Would it be more helpfull for the application writer if libnodave library reports when the underlying connection is not valid anymore.
Added classes that I am currently using to get around this problem. Hopefully these are helpfull to someone else dealing with this kind of problem also.
Basically I have wrapped input and output streams which I am providing to the PLCinterface in order to catch the exceptions I am getting from the streams. These wrapper classes picks up the exceptions and notifies the errormanager that there is a problem in a plc connection and so I can start re-establishing the connection. If more thorough explanation is needed please contact me.
And of course better solution would be to fix this issue in libnodave it self.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Added classes that I am currently using to get around this problem. Hopefully these are helpfull to someone else dealing with this kind of problem also.
Basically I have wrapped input and output streams which I am providing to the PLCinterface in order to catch the exceptions I am getting from the streams. These wrapper classes picks up the exceptions and notifies the errormanager that there is a problem in a plc connection and so I can start re-establishing the connection. If more thorough explanation is needed please contact me.
And of course better solution would be to fix this issue in libnodave it self.