No description
31dd434136
Draining the buffer is the correct appraoch to avoid accumulating data in the kernel unnecessarily. But it also reduces the overhead of reparsing the incoming data for message boundaries. The client that is to parse the data should parse as many messages as possible and remove them from the socket buffer. Finally, we probably need to cap the maximum buffer size to avoid bloating. However this heavily depends on the application's max message size, assuming there is no separate buffer beyond that of the socket to accumulate the messages in. Change-Id: I49c4eccebd474cd07ca84f3f4eae33bc717ed1f2 Reviewed-on: https://gerrit.libreoffice.org/34411 Reviewed-by: Ashod Nakashian <ashnakash@gmail.com> Tested-by: Ashod Nakashian <ashnakash@gmail.com> |
||
|---|---|---|
| bundled/include/LibreOfficeKit | ||
| common | ||
| debian | ||
| etc | ||
| kit | ||
| loleaflet | ||
| net | ||
| scripts | ||
| test | ||
| tools | ||
| wsd | ||
| .clang-tidy | ||
| .gitignore | ||
| .gitreview | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| configure.ac | ||
| COPYING | ||
| discovery.xml | ||
| favicon.ico | ||
| INSTALL | ||
| loolstat | ||
| loolwsd-systemplate-setup | ||
| loolwsd.service | ||
| loolwsd.spec.in | ||
| loolwsd.xml.in | ||
| Makefile.am | ||
| maketarballfordeb.sh.in | ||
| NEWS | ||
| PROBLEMS | ||
| README | ||
| robots.txt | ||
| sysconfig.loolwsd | ||
| TODO | ||
LibreOffice Online. This project has several components: wsd/ The Web Services Daemon - which accepts external connections. kit/ The client which lives in its own chroot and renders documents. common/ Shared code between these processes. loleaflet/ The client side JavaScript component. It is recommended to read these files: wsd/README loleaflet/README Enjoy.