-
|
@int2001 Looking at WLGate's websocket support with wavelogs new dxcluster. Reviewing the PR #2434 and looking at Line 91 in 6fc9bf0 wavelog Which works if both are running on the same machine, but doesn't work if you cloud host your wavelog. Have you considered if wavelog could host the websocket server or possibly a companion service/docker container? My thought is:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
Negative. |
Beta Was this translation helpful? Give feedback.
-
|
bravo, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Why do we need WLGate as intermediary? Couldn't Wavelog (or the user's browser) send commands to a local rigctld server directly? |
Beta Was this translation helpful? Give feedback.
-
|
nope. impossible with modern browsers due to security things. PS: Only (not built) alternative would be a Browser-Plugin. But tbh: Much more effort needed to support all Browsers. There are many 3rd party intermediary-tools from the community available, see: https://github.com/wavelog/Wavelog/wiki/Third-Party-Tools |
Beta Was this translation helpful? Give feedback.
Negative.
the Browsers JS-Engine connects to localhost. Not your Wavelog-Instance.
it doesn't matter if you host your Wavelog only in LAN or at some hoster or even in the cloud. Connection is made from Browser (your device) to WLGate on localhost.