You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking that maybe there is a way to remove the need for an additional json file that OTA uses to decide wether there is upgrade required. If the bin file HTTP headers would contain a version number, this could be enough to make a choice. This would be handled an other version of the execHTTPCheck() that reads header info instead of JSON, or maybe if it is an octet-stream, not json, then it would check the headers for version info.
What do you think? Maybe I am biased as I am hosting my bin firmware files on Google Storage Buckets, and it is easy to set headers there. 😄
András
The text was updated successfully, but these errors were encountered:
And it is the correct MVP, as without the json solution, you cannot make this work on every environment. Json makes it possible to do this FOTA in cases when you cannot manipulate headers. Which is the case for the majority of our users who will use some kind of cloud solution, like Dropbox, etc.
When my time allows, I will make a PR for you to review.
Hello,
I was thinking that maybe there is a way to remove the need for an additional json file that OTA uses to decide wether there is upgrade required. If the bin file HTTP headers would contain a version number, this could be enough to make a choice. This would be handled an other version of the execHTTPCheck() that reads header info instead of JSON, or maybe if it is an octet-stream, not json, then it would check the headers for version info.
What do you think? Maybe I am biased as I am hosting my bin firmware files on Google Storage Buckets, and it is easy to set headers there. 😄
András
The text was updated successfully, but these errors were encountered: