I'm not sure whether this is critical, so it has probably low priority.
Anyway... in case we restart the PBRcontrol, it automatically loses information about which data have already been checked. It is natural since this information is only stored "in code" when it is running. Then when get_log is called again, all available data from DB are provided.
This could be solved in two ways:
- the information is stored in DB
- it could be solved on
Bioarineo side - when connection stops working I will remember the last time stamp when I obtained some data, if I reconnect I will call get_log with the time stamp.
For solution 2, however, we would need some "ping" function which I could use to check whether the PBRcontrol is accessible again (pinging the server is not enough, it does not imply the tool is running too).
Any other ideas or preferences?
I'm not sure whether this is critical, so it has probably low priority.
Anyway... in case we restart the
PBRcontrol, it automatically loses information about which data have already been checked. It is natural since this information is only stored "in code" when it is running. Then whenget_logis called again, all available data from DB are provided.This could be solved in two ways:
Bioarineoside - when connection stops working I will remember the last time stamp when I obtained some data, if I reconnect I will callget_logwith the time stamp.For solution 2, however, we would need some "ping" function which I could use to check whether the
PBRcontrolis accessible again (pinging the server is not enough, it does not imply the tool is running too).Any other ideas or preferences?