Consider sending each submissions of prekey messages/client and prekey profiles as its own its own physical network message

otrv4 / otrv4-prekey-server

The Prekey Server specification as needed for the OTRv4 specification. This is a mirror of https://bugs.otr.im/otrv4/otrv4-prekey-server

2 stars 0 forks source link

Consider sending each submissions of prekey messages/client and prekey profiles as its own its own physical network message #13

Closed claucece closed 6 years ago

claucece commented 6 years ago

Can you clarify this @olabini ?

I guess this means that as a publisher you send a DAKE_3 + n prekey messages, and the network can send each prekey message one at the time.. is that so?

olabini commented 6 years ago

Yeah, something like that. Basically very very lightweight fragmentation. The way I think about it is that the N prekey messages will form a long long byte array. That array can be divided up however the client sees fit, into smaller network messages. The only thing the server needs to know is N, and then the actual data can flow, independent of how many actual network messages are used.