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
Currently (as of #8) new data (when notification to a client fails) is appended to a flash circular buffer, and then when the client becomes available it is pulled out from the front in a FIFO format and sent to the client. #8 details a number of issues with this implementation, but it is the best way to meet the current requirements (i.e. all the data is sent through a notification the same way that new samples are).
I propose a different system where data is simply appended to a file on a littlefs mount, and the client will download it when needed, possibly leveraging mcumgr to handle this. This comes with some additional corner cases, but it will be a much more scalable solution.
New data can still be sent through the notification when the client is available.
The text was updated successfully, but these errors were encountered:
Currently (as of #8) new data (when notification to a client fails) is appended to a flash circular buffer, and then when the client becomes available it is pulled out from the front in a FIFO format and sent to the client. #8 details a number of issues with this implementation, but it is the best way to meet the current requirements (i.e. all the data is sent through a notification the same way that new samples are).
I propose a different system where data is simply appended to a file on a littlefs mount, and the client will download it when needed, possibly leveraging mcumgr to handle this. This comes with some additional corner cases, but it will be a much more scalable solution.
New data can still be sent through the notification when the client is available.
The text was updated successfully, but these errors were encountered: