It would be nice if LibreOffice online could have a config option wherein document session termination could be reported back to the document server. So a url could be provided per document host (relative or full) for LOOL to report back. e.g <host desc="Regex pattern of hostname to allow or deny." allow="true"> <url>my.domain.co.uk</url> <session_termninate_url desc="Provide full url if not relative to host.url" relative="true"> /document/${docID}/terminated </session_termninate_url> </host>
We already provide a post message to the outer frame, i.e., the document server when the document session is terminated. Hosts can make use of that.
I'm currently poring through the logs looking for this message. Do you send this post message to the WOPI files endpoint (<host_url>/wopi/files/{fileId}/contents ) or to the server URL.
After a conversation with Pranavk it would seem I need to elaborate further. The issue can be described thus. In a scenario where integration is with a Document Management System (DMS), wherein a document is embedded in a lifecycle, it could be desired to halt a process regarding a document that is under collaborative editing by placing a locking mechanism on the document during editing (For instance prevent checkout but not the additional joining of users to the document session). However because document views can be terminated in numbers of ways which can circumvent reporting by the PostMessage mechanism, it would be beneficial if the wsd could report it's termination of a document session (i.e. when document has 0 sessions left) to the document host (possible via a configuration element where a path can be given relative to host url as mentioned initially, for example), such that the host could then simply make use of the information as it sees fit. From the logs: [1] wsd-15823-15831 11:42:12.828411 [ prisoner_poll ] INF ~DocumentBroker [/document-host-path/wopi/files/3032e206-0331-4815-aab9-2f6c01257be9] destroyed with 0 sessions left.| wsd/DocumentBroker.cpp:345 The document host could be notified of the same message, when it the above piece of information is also printed in the logs.
@Pranav, any opinion here?
This enhancement has been in UNCONFIRMED status for a while, moving it to NEW... Note to the reporter: Changing the status to NEW doesn't mean the enhancement is going to be implemented. In order to do so, either you implement it yourself, you find someone to do it for you or you get professional support < https://www.libreoffice.org/get-help/professional-support/ >