No description
05c2782a81
The wakeup() call in SocketPoll::stop() doesn't always (or ever?) actually cause the wakeup code to be invoked and callbacks called right after, and we don't want to risk the leftover callbacks being invoked when the same SocketPoll object is started again. (This did actually happen.) In a normal Online, this is not a problem, as SocketPolls aren't reused. One document per kit process, a separate kit process for each document. Not so in a mobile app, there we have just one process that handles document after document as the user closes one, opens another (or the same anew), etc. |
||
---|---|---|
bundled/include/LibreOfficeKit | ||
common | ||
debian | ||
docker | ||
etc | ||
gtk | ||
ios | ||
kit | ||
loleaflet | ||
man | ||
Mobile | ||
net | ||
scripts | ||
test | ||
tools | ||
wsd | ||
.clang-tidy | ||
.gitignore | ||
.gitreview | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
configure.ac | ||
COPYING | ||
discovery.xml | ||
favicon.ico | ||
INSTALL | ||
loolkitconfig.xcu | ||
loolstat | ||
loolwsd-systemplate-setup | ||
loolwsd.service | ||
loolwsd.spec.in | ||
loolwsd.xml.in | ||
Makefile.am | ||
NEWS | ||
PROBLEMS | ||
README | ||
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.