Messages are scheduled using a function that returns a promise which is resolved after messages are sent.
https://linear.app/comm/issue/ENG-8674/track-progress-of-sending-tunnelbroker-messages
Depends on D12776
Differential D12786
[lib] Track progress of message processing Authored by tomek on Jul 17 2024, 5:54 PM. Tags None Referenced Files
Subscribers
Details
Messages are scheduled using a function that returns a promise which is resolved after messages are sent. https://linear.app/comm/issue/ENG-8674/track-progress-of-sending-tunnelbroker-messages Depends on D12776 Tested on both native and web. Added some code await this.props.p2p.sendDMOperation({
op: {
type: 'send_text_message',
threadID: messageInfo.threadID,
creatorID: messageInfo.creatorID,
time: messageInfo.time,
messageID: getUUID(),
text: messageInfo.text,
},
supportsAutoRetry: false,
recipients: 'self_devices',
});to input state containers so that it is called after sending messages. Checked if the second device received a message after sending a text message.
Diff Detail
Event TimelineComment Actions I wonder what the difference is between our terms "P2P messages" and "DM"s I think "P2P messages" cover a superset of DMs – it's basically all client-to-client messages that are encrypted and passed via Tunnelbroker. Does that sound right? And is it consistent with our usage here? Comment Actions Yes, I agree - "P2P messages" cover a superset of DMs. What I'm describing here is sending P2P messages generated from a single DM operation. I'm going to review the naming and make sure it isn't confusing. Comment Actions I think the usage of if and dmOpID can be improved and more descriptive, this might look confusing as we have plenty IDs all over the codebase - but I don't have idea about better ones
| |||||||||||||||||||||||||||||||||||