No description
bc7decb6ca
Having a separate "disconnect" message is a disgrace. There should be no need for it. WebSocket has a perfectly fine graceful disconnect mechanism already (CLOSE frames). The code needs to be prepared to receive a CLOSE frame at any time. The code also needs to be prepared for the underlying socket being bluntly closed by the other end, without sending any WebSocket CLOSE frame. The only sane thing is to handle a "disconnect" message in the same way as those situations anyway, so why is it needed? |
||
---|---|---|
loleaflet | ||
loolwsd | ||
.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.