-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] local address for server #175
Comments
I'll add that this would be incredibly useful for those of us trying to be careful about server bandwidth or home Internet data usage. I would love to set a transcoding policy based on whether Tempo is connected over LAN or WAN. |
Hi, I have implemented the addition of the local address to which to connect instead of using the main address. The algorithm is something like this: If connected to the main address, try to connect to the local address after a fixed X amount of time has passed. If the latter can be reached, use the local one, otherwise continue using the main one. If the main one is also not reachable then I present a warning message about the unreachability of the server. The check on which type of connection to use is done every time you enter the app, after a pre-established X time. At the moment I don't think I will implement an option for ad hoc transcoding by type of address used since the transcoding option by type of connection used already exists. I think this type of control is "stronger" than the previous one. |
The functionality still needs to be fully tested before we can release it, but if you prefer you can test it. |
Please add a local address for the server like dsub uses. When available, connect and use the local server; when not available, connect over the internet.
There's several ways to implement this:
The text was updated successfully, but these errors were encountered: