-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add a failover if error occurs when push data #23
Comments
At first i liked the idea. But the longer i'm thinking about it, questions are coming up: i mean: If you are doing FT8 with WJST-X, the WSJT-X creates his own ADIF regardless if reporting to UDP (for WLGate) is set nor not. You can simply upload the WSJT-X-ADIF to Wavelog. With it's automatic dupe-check only the new ones are going to be added to Wavelog. Or i am wrong here? |
Thanks for consideration ! Indeed, but :
New idea : maybe just ask for a folder instead a file path, and make error files like : |
Risk that those files are ignored by OP is the same as at WSJT-X. |
I agree, but the case of a down WaveLog server or instable network are exceptions, and user knows where the folder is, the file or folder can be purged after import. Maybe add the feature as optional with a check box to enable it if needed ? Thanks for consideration, |
Why not simply add a retry button for another push? No need for an ADIF. |
If we add a "Retry"-Button, we need to implement some kind of queuing into it. WavelogGate is a simple "transporter" for ADIFs. Never meant to be a buffering/queuing/dequeuing system. the paradigm for WLGate was (and is): Keep it as simple as possible. |
Why do you think so complicated - no offense! EVERY variant you mentioned has the same problem now. When you are not connected to the internet, everything fails. My problem is, that out of 100 QSO's 1 fails to upload because of timeout. If this happens, a simple retry button would be enough. No need for buffering, because when it is failed, it is still buffered, because it is still on the screen, just red and not green. |
@oe3gwu - feel free to implement it. but please consider "simpleness" as well and failover-mechanisms. It needs to be bulletproof. Otherwise there will be support-questions over and over. that's one of the benefits OpenSource provides. You can fork, implement it and give something back via a PR. No offense meant ;) Just showing a way how to achieve it. [Edit because reacting to "y do you think so overcomplicated]: Software-development is only 10% real coding. it's 90% brainwork. Checking side-effects, checking support-loads and so on. |
Honestly if I would be a programmer, I would do it myself. But I am not! |
And I am doing these things during my spare time as a hobby :) |
Hi! First, thanks for WaveLogGate & Wavelog, awesome stack.
Is it possible to add a failover behavor if Internet connection fail or timeout occurs ?
WaveLogGate/main.js
Line 200 in 875e996
WaveLogGate/main.js
Line 207 in 875e996
My idea is simple : write the QSO in a local ADIF file if error, so it'll be easy to import the file when back home.
I can try to implement this but I'm not very used to compiling JS for cross-platform, I use/prefer Golang for this kind of interfaces.
Thanks,
The text was updated successfully, but these errors were encountered: