Page MenuHomePhabricator

Rename cookieID -> cryptoID and deviceToken -> deliveryID
AcceptedPublic

Authored by marcin on Tue, Jun 11, 10:45 AM.
Tags
None
Referenced Files
F2110240: D12398.id41556.diff
Tue, Jun 25, 7:09 PM
Unknown Object (File)
Mon, Jun 24, 7:12 PM
Unknown Object (File)
Sat, Jun 22, 2:56 PM
Unknown Object (File)
Fri, Jun 21, 7:28 PM
Unknown Object (File)
Fri, Jun 21, 6:43 AM
Unknown Object (File)
Thu, Jun 20, 9:08 PM
Unknown Object (File)
Thu, Jun 20, 7:38 AM
Unknown Object (File)
Tue, Jun 18, 3:45 AM
Subscribers

Details

Reviewers
kamil
tomek
Summary

This differential renames cookieID -> cryptoID and deviceToken -> deliveryID in keyserver and lib push related files. After moving notif generation and encryption to lib deviceToken and cookieID are no longer valid they should be replaced with something more generic.

Test Plan
  1. Flow
  2. Test all notifs for all platforms and large notifs as well.

Diff Detail

Repository
rCOMM Comm
Branch
marcin/eng-8282
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Probably you know it better so up to you but for me recipientID seems better than cryptoID

This revision is now accepted and ready to land.Wed, Jun 19, 3:32 PM

Probably you know it better so up to you but for me recipientID seems better than cryptoID

cryptoID is the id of the olm session to use to encrypt notification. On the native olm sessions will be matched by deviceID which will also be the id of the recipient. But on the keyserver recipientID would rather mean deviceToken, byt encryption is done based on cookieID.