This repository has been archived by the owner on May 26, 2022. It is now read-only.

Further optimisations and correctness fixes #77

Closed

raulk opened this issue Apr 24, 2020 · 1 comment

Assignees

Member

raulk commented Apr 24, 2020

See follow-up comments on #58. Some highlights:

goroutine to monitor the context if a deadline is set, and close the connection if it fires.
get rid of readMsgInsecure and writeMsgInsecure abstractions so we can control the buffers.
on read, if there are no queued bytes, and the user-provided buffer is large enough, read and decrypt in place. (requires peeking the length of the incoming payload).
handshake messages can probably reuse buffers -- their lengths should be predictable.

The text was updated successfully, but these errors were encountered:

raulk mentioned this issue

Fix Read() behaviour; heavy performance optimisations; i/o deadlines; more #58

Merged

aarshkshah1992 self-assigned this

aarshkshah1992 mentioned this issue

Further Optimizations and refactor benchmarking code #81

Merged

Contributor

marten-seemann commented May 25, 2022

Fixed by #81?

marten-seemann closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.