Common solutions:
Personally as a user I prefer the 1st or 4th option, because I want to keep the function if the service goes down. (Some people are nice and they allow you to patch a local version of the remote service via custom DNS at end of life.) However this is not practical for all users. The 2nd option creates a lot of cost and security issues if not well thought out. With the first and fourth options the user is responsible for managing these.
All of these work remotely. (If you include VPN.) Bluetooth would not but could be made to work with one of these.
- Local server (Device broadcasts and server answers, user interacts with server)
- Remote server (Device dials out to domain name, user interacts with server)
- Small LCD
- Make it static (user changes it later)
- DNS or hostname (may require special server and may not support multiple instances well)
Personally as a user I prefer the 1st or 4th option, because I want to keep the function if the service goes down. (Some people are nice and they allow you to patch a local version of the remote service via custom DNS at end of life.) However this is not practical for all users. The 2nd option creates a lot of cost and security issues if not well thought out. With the first and fourth options the user is responsible for managing these.
All of these work remotely. (If you include VPN.) Bluetooth would not but could be made to work with one of these.
Statistics: Posted by dthacher — Thu Feb 08, 2024 7:30 am