Page MenuHomePhabricator

[lib] handle `IdentityDeviceListUpdated` P2P message
ClosedPublic

Authored by kamil on Mon, Jun 10, 4:54 AM.
Tags
None
Referenced Files
F2173754: D12376.id41156.diff
Tue, Jul 2, 10:43 PM
Unknown Object (File)
Mon, Jul 1, 2:56 AM
Unknown Object (File)
Sun, Jun 30, 12:19 AM
Unknown Object (File)
Wed, Jun 26, 2:29 PM
Unknown Object (File)
Mon, Jun 24, 8:38 AM
Unknown Object (File)
Sun, Jun 23, 5:59 PM
Unknown Object (File)
Sat, Jun 22, 4:33 AM
Unknown Object (File)
Fri, Jun 21, 7:34 AM
Subscribers

Details

Summary

Part of ENG-7837.

Client code to handle message from Identity.

Depends on D12375, D12374, D12372

Test Plan

Tested in D12378.

Diff Detail

Repository
rCOMM Comm
Branch
peer-list-3
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Mon, Jun 10, 9:51 AM
tomek added inline comments.
lib/selectors/user-selectors.js
225

We should explain in a comment what we mean by foreign peer devices.

236–239

This doesn't hurt, but we don't need to repeat a condition that was used while filtering

lib/tunnelbroker/use-peer-to-peer-message-handler.js
222

Talked with @kamil about this call. This broadcast will happen on all the devices and not just on the primary. This isn't a correctness concern, because the payload doesn't include a device list and thus can't be outdated. From the performance point of view, this is wasteful but doesn't hurt us too much. But still, we can consider limiting the broadcast to be sent only from the primary.

222–223

We can consider broadcasting also to our devices which will simplify the logic a bit, but it's up to you.

This revision is now accepted and ready to land.Thu, Jun 13, 3:04 AM
  • add comment
  • remove obsolete condition
lib/tunnelbroker/use-peer-to-peer-message-handler.js
222–223

Leaving as it is to avoid sending data trough network when we can handle it locally