Page MenuHomePhabricator

[lib] handle Tunnelbroker messages sequentially
ClosedPublic

Authored by kamil on Apr 22 2024, 5:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 24, 7:18 AM
Unknown Object (File)
Tue, Dec 24, 7:18 AM
Unknown Object (File)
Tue, Dec 24, 7:18 AM
Unknown Object (File)
Tue, Dec 24, 7:18 AM
Unknown Object (File)
Tue, Dec 24, 7:17 AM
Unknown Object (File)
Nov 12 2024, 3:52 AM
Unknown Object (File)
Nov 11 2024, 7:52 PM
Unknown Object (File)
Nov 7 2024, 4:14 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
Lint
Lint Not Applicable
Unit
Tests Not Applicable

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.Apr 29 2024, 12:26 AM
lib/tunnelbroker/tunnelbroker-context.js
282–289 ↗(On Diff #39383)

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

lib/tunnelbroker/tunnelbroker-context.js
282–289 ↗(On Diff #39383)

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

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