Ashod Nakashian 3decba7eec wsd: specify the minimum bytes we can write to the socket ... When writing to the socket, it's always more efficient to fill the buffer up to the hardware limit for each write. This is doubly important for efficiency with SSL, due to the overhead of encrypting multiple small buffers instead of one large one. Currently we don't write more than one message at a time, primarily due to limitations in the Poco sockets in the unit-tests, which have a hard time consuming multiple WS frames with a single poll (subsequent calls to poll doesn't enter signalled state until new data arrives, possibly because the data is read and buffered internally, making the whole scheme of using poll unreliable and meaningless). Change-Id: Ic2e2cf1babfb5ab4116efd93f392977ba234d92b Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>		2021-04-27 17:48:23 -04:00
..
Config.cpp
Connect.cpp	wsd: test: better logging	2021-03-08 22:49:53 -05:00
KitClient.cpp
map.cpp	wsd: simplify and document dumpHex	2021-03-13 19:34:02 -05:00
mount.cpp
Replay.hpp
Stress.cpp	wsd: cleanup Poco headers	2021-03-22 10:09:22 -04:00
Tool.cpp
WebSocketDump.cpp	wsd: specify the minimum bytes we can write to the socket	2021-04-27 17:48:23 -04:00