Page MenuHomePhabricator

[lib] handle Tunnelbroker messages sequentially
ClosedPublic

Authored by kamil on Apr 22 2024, 5:57 PM.
Tags
None
Referenced Files
F1834154: D11732.id39652.diff
Thu, May 23, 3:38 PM
F1834152: D11732.id39645.diff
Thu, May 23, 3:38 PM
F1834151: D11732.id39383.diff
Thu, May 23, 3:38 PM
F1834127: D11732.id.diff
Thu, May 23, 3:37 PM
F1834088: D11732.diff
Thu, May 23, 3:37 PM
Unknown Object (File)
Sat, May 18, 3:01 PM
Unknown Object (File)
Sat, May 18, 3:35 AM
Unknown Object (File)
Tue, May 7, 10:39 AM
Subscribers

Details

Summary

This is similar approach to what's implemented on web worker: https://phab.comm.dev/D11299

Test Plan

Connect two devices, send message trough Tunnelbroker and add sleep to processing, make sure each messages are processed in sequence.

Diff Detail

Repository
rCOMM Comm
Branch
publish-receiver
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Apr 23 2024, 6:43 AM
This revision is now accepted and ready to land.Mon, Apr 29, 12:26 AM
lib/tunnelbroker/tunnelbroker-context.js
282–289

Wondering how this would behave if one of the calls to peerToPeerMessageHandler fails.

lib/tunnelbroker/tunnelbroker-context.js
282–289

peerToPeerMessageHandler should fail/throw - to confirm message to TB regardless of success or error while processing

kamil requested review of this revision.Mon, Apr 29, 4:57 AM
This revision is now accepted and ready to land.Mon, Apr 29, 5:31 AM