Page MenuHomePhabricator

[web] Rename database worker
ClosedPublic

Authored by michal on Mar 4 2024, 7:19 AM.
Tags
None
Referenced Files
F3380238: D11236.id38133.diff
Wed, Nov 27, 10:16 PM
Unknown Object (File)
Wed, Nov 27, 3:01 PM
Unknown Object (File)
Wed, Nov 27, 12:02 PM
Unknown Object (File)
Tue, Nov 26, 6:59 PM
Unknown Object (File)
Sun, Nov 24, 11:46 PM
Unknown Object (File)
Thu, Nov 7, 3:08 AM
Unknown Object (File)
Oct 20 2024, 11:51 PM
Unknown Object (File)
Oct 18 2024, 1:40 AM
Subscribers

Details

Summary

ENG-6648 : Refactor database worker

The database worker will now contains code not related to the database (e.g. cryptoStore and other crypto related operations) so I'm renaming it to a general shared-worker.

Depends on D11143

Test Plan

Check that the app works, click around, check that the database works.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

michal requested review of this revision.Mar 4 2024, 7:34 AM

Are you sure this change is fully backward compatible? Looks like yes but want to confirm

web/app.react.js
123 ↗(On Diff #37782)
This revision is now accepted and ready to land.Mar 4 2024, 8:45 AM

Fixed comment. Also renamed the worker name from comm-app-database-${codeVersion} to comm-app-shared-worker-${codeVersion}.

Are you sure this change is fully backward compatible? Looks like yes but want to confirm

I don't think we expose the shared worker to e.g. keyserver. It should be fully an "implementation detail" for the webapp codebase (except for the moment when the app loads the worker code at the start). If there are multiple tabs open the mismatch will be handled like the version mismatch -> the workers have different names so they shouldn't collide.