Commit ed7e76f3 authored by Vincent Pelletier's avatar Vincent Pelletier

Add a TODO about data checksums.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2598 71dcc9de-d417-0410-9af5-da40c76e7ee4
parent 10c96d61
...@@ -149,6 +149,14 @@ RC - Review output of pylint (CODE) ...@@ -149,6 +149,14 @@ RC - Review output of pylint (CODE)
- tpc_finish failures propagation to master (FUNCTIONALITY) - tpc_finish failures propagation to master (FUNCTIONALITY)
When asked to lock transaction data, if something goes wrong the master When asked to lock transaction data, if something goes wrong the master
node must be informed. node must be informed.
- Verify data checksum on reception (FUNCTIONALITY)
In current implementation, client generates a checksum before storing,
which is only checked upon load. This doesn't prevent from storing
altered data, which misses the point of having a checksum, and creates
weird decisions (ex: if checksum verification fails on load, what should
be done ? hope to find a storage with valid checksum ? assume that data
is correct in storage but was altered when it travelled through network
as we loaded it ?).
Master Master
- Master node data redundancy (HIGH AVAILABILITY) - Master node data redundancy (HIGH AVAILABILITY)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment