Page MenuHomePhabricator

[lib] handle Tunnelbroker messages sequentially
ClosedPublic

Authored by kamil on Apr 22 2024, 5:57 PM.
Tags
None
Referenced Files
F2109661: D11732.id39652.diff
Tue, Jun 25, 5:14 PM
Unknown Object (File)
Sat, Jun 22, 6:35 PM
Unknown Object (File)
Sat, Jun 22, 6:35 PM
Unknown Object (File)
Sat, Jun 22, 6:35 PM
Unknown Object (File)
Sat, Jun 22, 6:35 PM
Unknown Object (File)
Sat, Jun 22, 6:35 PM
Unknown Object (File)
Wed, Jun 19, 3:31 PM
Unknown Object (File)
Wed, Jun 19, 11:16 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.Apr 29 2024, 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.Apr 29 2024, 4:57 AM
This revision is now accepted and ready to land.Apr 29 2024, 5:31 AM