No description
Find a file
Tor Lillqvist bc7decb6ca No "disconnect" message is sent by our client JS code (and that is good)
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?
2016-02-24 17:44:17 +02:00
loleaflet loleaflet: bump version after tarball 2016-02-24 14:10:18 +01:00
loolwsd No "disconnect" message is sent by our client JS code (and that is good) 2016-02-24 17:44:17 +02:00
.gitreview Add git-review config 2015-11-20 17:13:26 +01:00
README Reformatted loolwsd README. 2015-04-21 12:48:17 +02:00

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.