37d0105c83
This change only affects clients that are subscribed to events, which should be the main cause of our problems. In the common case (no buffered data) the behaviour doesn't change at all: the message is sent directly, no ev_io / ev_timeout callback is enabled. Once a write to a client's socket is not completed fully (returns with EAGAIN error), we put the message in the tail of a queue and init an ev_io callback and a corresponding timer. If the timer is triggered first, the socket is closed and the client connection is removed. If the socket becomes writeable before the timeout we either reset the timer if we couldn't push all the buffered data or completely remove it if everything was pushed. We could also replace ipc_send_message() for all client connections in i3, not just those subscribed to events. Furthermore, we could limit the amount of messages stored and increase the timeout (or use multiple timeouts): eg it's ok if a client is not reading for 10 seconds and we are only holding 5KB of messages for them but it is not ok if they are inactive for 5 seconds and we have 30MB of messages held. Closes #2999 Closes #2539 |
||
|---|---|---|
| .github | ||
| AnyEvent-I3 | ||
| contrib | ||
| debian | ||
| docs | ||
| etc | ||
| i3-config-wizard | ||
| i3-dump-log | ||
| i3-input | ||
| i3-msg | ||
| i3-nagbar | ||
| i3bar | ||
| include | ||
| libi3 | ||
| m4 | ||
| man | ||
| parser-specs | ||
| share | ||
| src | ||
| testcases | ||
| travis | ||
| .clang-format | ||
| .editorconfig | ||
| .gitignore | ||
| .travis.yml | ||
| DEPENDS | ||
| I3_VERSION | ||
| LICENSE | ||
| Makefile.am | ||
| PACKAGE-MAINTAINER | ||
| README.md | ||
| RELEASE-NOTES-4.15 | ||
| configure.ac | ||
| generate-command-parser.pl | ||
| i3-dmenu-desktop | ||
| i3-migrate-config-to-v4 | ||
| i3-save-tree | ||
| i3-sensible-editor | ||
| i3-sensible-pager | ||
| i3-sensible-terminal | ||
| logo.svg | ||
| pseudo-doc.doxygen | ||
| release.sh | ||
README.md
i3: A tiling window manager
i3 is a tiling window manager for X11.
For more information about i3, please see the project's website and online documentation.
For information about contributing to i3, please see CONTRIBUTING.md.