Hi there,
In our firmware we have a layer on top of FDS that handles higher level file system functionality. There is room for improvement in this layer that we created, but before making too many changes we thought it would be better to see if Nordic has any plans to implement some of these features already:
- Reading a record position too soon after a delete or write operation can cause unexpected behavior (the file may still exist or have old data) since reads are asynchronous.
- There could be an optional blocking delete/write
- There could be a read that is blocking, and doesn't read until delete/write operations are completed
- There could be a non-blocking read that occurs on a callback for when all delete/write operations are done
- If there was a reliable way to tie specific delete/write operations to their resulting events we could have callbacks for specific operations
- It may be useful to have a callback or event for when the FDS queue is empty
- This could be used in the above mentioned case
Thanks!
