The Flashboard updater thread encounters a problem with blocking tasks which stop the updater for too long. The blocking tasks are the retreival of the ip address for communications (both comm and cam). If the remote is not reachable, this task could take up to 5 seconds. If only using a part of flashboard communications, the other will cause issues.
An option to solve this is to create a separate thread for heavy duty tasks. But! this means another thread, which might be too much already.
It is possible to manually avoid such issue by making sure that when not using a part of flashboard, its defined host name is an empty string.
Added an address retrieval thread which runs and retrieves the address from host names. To save resources, the thread is put into long sleep cycles when not needed.
The Flashboard updater thread encounters a problem with blocking tasks which stop the updater for too long. The blocking tasks are the retreival of the ip address for communications (both comm and cam). If the remote is not reachable, this task could take up to 5 seconds. If only using a part of flashboard communications, the other will cause issues.
An option to solve this is to create a separate thread for heavy duty tasks. But! this means another thread, which might be too much already. It is possible to manually avoid such issue by making sure that when not using a part of flashboard, its defined host name is an empty string.