Page MenuHomePhabricator

[web][native] persist Outbound P2P messages when processing store ops
ClosedPublic

Authored by kamil on May 20 2024, 4:20 PM.
Tags
None
Referenced Files
F3348581: D12130.id40421.diff
Fri, Nov 22, 3:16 PM
F3346759: D12130.diff
Fri, Nov 22, 9:46 AM
Unknown Object (File)
Fri, Nov 8, 10:39 PM
Unknown Object (File)
Oct 23 2024, 5:26 AM
Unknown Object (File)
Oct 23 2024, 4:01 AM
Unknown Object (File)
Oct 20 2024, 2:08 AM
Unknown Object (File)
Oct 20 2024, 1:52 AM
Unknown Object (File)
Oct 19 2024, 9:42 PM
Subscribers

Details

Summary

It's important to address messages to the other peers in the same SQLite transaction as updating our own store (we don't have state-sync yet so this allows us to make sure data is consistent).

Later on, this data will be encrypted and sent through Tunnelbroker (D12132).

Depends on D12129

Test Plan

Make sure messages are persisted (added some mock and read it later).
Tested end-to-end in: D12133

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.May 21 2024, 1:23 AM
kamil edited the summary of this revision. (Show Details)
kamil edited the summary of this revision. (Show Details)
kamil edited the test plan for this revision. (Show Details)
kamil added inline comments.
native/cpp/CommonCpp/NativeModules/CommCoreModule.cpp
430–469

I guess this could be extracted to a separate function but wondering what reviewers think

This revision is now accepted and ready to land.May 23 2024, 6:38 AM