ec6898f1ab
This may increase processing latency a bit, particularly with large attachments, but will ensure that messages are dispatched in the order they are received. It would be nice to enforce ordering on only the dispatch step, so that we could, for example, decrypt the next websocket message while waiting for an attachment to download, but that will require a more complicated refactor. Will stick with the quick fix for now and revisit later. Fixes #342 // FREEBIE |
||
---|---|---|
.. | ||
storage | ||
test | ||
account_manager.js | ||
api.js | ||
axolotl_wrapper.js | ||
components.js | ||
contacts_parser.js | ||
crypto.js | ||
errors.js | ||
helpers.js | ||
key_worker.js | ||
libaxolotl.js | ||
message_receiver.js | ||
outgoing_message.js | ||
protobufs.js | ||
sendmessage.js | ||
storage.js | ||
stringview.js | ||
websocket-resources.js |