ladybird/Libraries/LibTLS
Andreas Kling 4b202a3c79 LibCore+LibTLS: Don't keep a "ready to write" notifier on all Sockets
The "ready to write" notifier we set up in generic socket connection is
really only meant to detect a successful connection. Once we have a TCP
connection, for example, it will fire on every event loop iteration.

This was causing IRC Client to max out the CPU by getting this no-op
notifier callback over and over.

Since this was only used by TLSv12, I changed that code to create its
own notifier instead. It might be possible to improve TLS performance
by only processing writes when actually needed, but I didn't look very
closely at that for this patch. :^)
2020-05-18 20:16:52 +02:00
..
ClientHandshake.cpp LibTLS: Verify server certificate expiry date 2020-05-07 10:23:58 +02:00
CMakeLists.txt Build: Switch to CMake :^) 2020-05-14 20:15:18 +02:00
Exchange.cpp LibTLS: Split TLSv12 to sensible categorical files 2020-05-02 12:24:10 +02:00
Handshake.cpp LibTLS: Implement build_alert() 2020-05-02 12:24:10 +02:00
Record.cpp LibTLS: Try to disambiguate errors in case of failure 2020-05-05 11:20:42 +02:00
Socket.cpp LibCore+LibTLS: Don't keep a "ready to write" notifier on all Sockets 2020-05-18 20:16:52 +02:00
TLSPacketBuilder.h LibTLS: Split TLSv12 to sensible categorical files 2020-05-02 12:24:10 +02:00
TLSv12.cpp LibCore+LibTLS: Don't keep a "ready to write" notifier on all Sockets 2020-05-18 20:16:52 +02:00
TLSv12.h LibCore+LibTLS: Don't keep a "ready to write" notifier on all Sockets 2020-05-18 20:16:52 +02:00