7 commits

Author	SHA1	Message	Date
Tor Lillqvist	7263491ea6	Document return value of our LOOLWebSocket::receiveFrame() ... Especially the -1 return value, which is different from what the Poco WebSocket::receiveFrame() can return.	2016-12-02 16:52:48 +02:00
Tor Lillqvist	f144dd9f05	Log also the frame as received	2016-12-02 16:52:48 +02:00
Tor Lillqvist	ffbc9baccc	Use getAbbreviatedFrameDump() instead of getAbbreviatedMessage() when logging ... The more information the better, when tracking problems.	2016-12-02 16:52:48 +02:00
Jan Holesovsky	9842f3239f	Make sure we don't use the jitter / delay in production builds. ... And default to 0 even for debug; who wants to use that for debugging, they know what to do. Change-Id: I23dd0c5f806b2b31a883b7a2b8d822ea8c0bb6c5	2016-11-28 11:31:06 +01:00
Ashod Nakashian	6ab32e0aa9	loolwsd: use larger threshold to large messages ... Messages larger than a certain size are preambled with a 'nextmessage' message that hold the size of the subsequent message. This is a workaround to a limitation the Poco WebSocket API where if the buffer size is smaller than the received frame the socket ends up in a bad state and must be closed. Unfortunately the new API that avoids this workaround is not yet released by Poco. Here we minimize the need for 'nextmessage' to truely large messages. The limit is now raised from above 1KB to over 63KB. We may raise this limit further, but that will cost each socket that much dedicated buffer size. Change-Id: I01e4c68cdbe67e413c04a9725152224a87ab8267 Reviewed-on: https://gerrit.libreoffice.org/31286 Reviewed-by: Ashod Nakashian <ashnakash@gmail.com> Tested-by: Ashod Nakashian <ashnakash@gmail.com>	2016-11-28 04:54:37 +00:00
Michael Meeks	c1a398977f	Adapt makefiles, includes etc. to new locations.	2016-11-25 09:58:57 +00:00
Michael Meeks	cca657c8f2	Apply the pre-branch rename script to re-organize the source.	2016-11-25 09:58:48 +00:00

Renamed from loolwsd/LOOLWebSocket.hpp (Browse further)