No description
ce64895cee
While there are two separate callbacks registered (one with lokit and the other with lokitDocument,) there is no reason why they should be handled separately (and indeed differently). The lokit callback only sends notifications on status indicator (during loading and saving) and document password type (if protected). Due to the different callback handlers the status indicator was only sent to the first client, not all (as one expects). Furthermore, because the lokit callback was processed on the Core thread, it was bound to cause performance and thread-safety issues. Specifically it deadlocked when another callback was in flight when a save issued status indicator callback. By unifying the callbacks and putting all callback messages on the message queue we avoid all of the above and simplify the code. Change-Id: I5bd790b6ce88b7939186c1ec1dead7fb6cabf7e0 Reviewed-on: https://gerrit.libreoffice.org/24522 Reviewed-by: Ashod Nakashian <ashnakash@gmail.com> Tested-by: Ashod Nakashian <ashnakash@gmail.com> |
||
|---|---|---|
| loleaflet | ||
| loolwsd | ||
| scripts | ||
| .gitreview | ||
| README | ||
LibreOffice on-line. This project fundamentally has two pieces: loolwsd/ The server side component. loleaflet/ The client side component. First compile loolwsd, and then loleaflet. Since you need both of these to get things working, it is recommended to read the READMEs in both projects. Enjoy.