You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the idea of this would be to execute in addition to the other trigger. For lockscreen, I see no issue.
However, for a shutdown trigger, I see an issue with the possibility that shutdown happens too fast before the query finishes. I'm not sure if the user would want to prioritize the URL query before the shutdown.
In the event that the usual trigger may prevent the HTTP query from finishing, I suppose the best thing to do is to:
Execute the lockscreen trigger immediately
Execute an asynchronous http query in the background
Wait a user-configurable timeout for the http query to finish. If it does not finish by the timeout, go ahead and trigger the shutdown trigger
A user just requested that we add a feature to the BusKill app to query some webpage on trigger.
This could be useful, for example, to trigger remote shutdown of other devices.
The text was updated successfully, but these errors were encountered: