The "Shared Link" source should cache the last fetched db in case the link is becomes unavailable. Currently it says "Network error" if the link goes down after a successful first fetch.
For example, it would be nice to set a lan source before going on a trip, but then be able to use that last fetched copy (visible to tusk only) when outside the lan, no matter if the machine is restarted.
In general, the online requirement makes shared links far less useful in other scenarios as well, for example with intermittent connectivity, firewalls, offline, etc.
subdavis
commented
6 years ago
This issue is a
feature
What is the expected behaviour
The "Shared Link" source should cache the last fetched db in case the link is becomes unavailable. Currently it says "Network error" if the link goes down after a successful first fetch.
For example, it would be nice to set a lan source before going on a trip, but then be able to use that last fetched copy (visible to tusk only) when outside the lan, no matter if the machine is restarted.
In general, the online requirement makes shared links far less useful in other scenarios as well, for example with intermittent connectivity, firewalls, offline, etc.
Thanks! - John