Feature Request: Direct Measurement Upload Without Local Storage

[markuskae]

Enable direct measurement upload without the need to save them on the computer first.

[R-Abbasi]

Do you mean instead of storing the buffers in msg:

std::string msg{ID};
// have each entry on a new line
msg += '\n';
msg += vinBuffer;
msg += '\n';
msg += milage;
// ...
if (ImGui::Button(" Send "))
{
    // example url
    const std::string url{"https://raw.githubusercontent.com/skunkforce/omniview/"};
    sendData(msg, url);
 }

use them directly for uploading:

if (ImGui::Button(" Send "))
{
    // example url
    const std::string url{"https://raw.githubusercontent.com/skunkforce/omniview/"};
    sendData(std::move(std::string(ID) + "\n" + vinBuffer + "\n" + milage), url);
 }

?

[AKMaily]

I believe he is referring to the current implementation. The data can be sent along with the message in the 'Generate Training Data' menu, even if the user has not saved the measurement before. @R-Abbasi

[AKMaily]

To address this issue, we need to implement two methods for sending data. Currently, sending data to the FFT API works regardless of whether the data has been saved or not, as the FFT API requires a JSON string. However, the battery API requires a file, necessitating that the data be saved, at least temporarily. The HUB API, on the other hand, accepts both approaches. @R-Abbasi, what are your thoughts on the best approach to handle all of these scenarios?

[R-Abbasi]

The data (measurement values and string literals) are all inserted into a JSNO object in memory and then sent to the server. The object will be destroyed at the end of its block automatically, so nothing is required to be saved on machine's disk using the Generate Training Data popup.
#142

[AKMaily]

For the HUB API a .csv file is required because this API does not expect a JSON but a .csv file. @R-Abbasi Only the analyze APIs currently require a JSON. Therefore we need to implement two ways to send the data to this different APIs in different formats. I would appreciate your insights on the most effective approach to accomplish this.

[R-Abbasi]

I'm not much experienced in networking but I guess the case is not that complex. If the data itself is sufficient for an API, we can put that data into a container and still use the http POST service to upload it. If an API needs a file in a specific format, that could also be handled using the FTP protocol, supposedly.