StorageManager thread-safe modifyData implementation #60
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#60
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As part of my investigation to implement decentralized datapools, I had a look at the pool implementation which will be used to store the datasets / variables locally.
UPDATE: maybe a std::map will be used, like with global pool
If raw access is needed, I will need a lock to accesss the data. The storage manager does not have a thread safe implementation of the
modifyData()
local pool function yet (and I guess this is required too?), so I would suggest to implement a call to it.related to #68
StorageManager modifyData implementationto StorageManager thread-safe modifyData implementationUpdate: modifyData not thread-safe, thread-safety is policy based.