libreoffice-online/loolwsd/Makefile.am

bin_PROGRAMS = loolwsd

loolwsd_SOURCES = LOOLWSD.cpp LOOLSession.cpp TileCache.cpp Util.cpp LOOLProtocol.cpp

noinst_PROGRAMS = loadtest connect

loadtest_SOURCES = LoadTest.cpp Util.cpp LOOLProtocol.cpp

connect_SOURCES = Connect.cpp  Util.cpp

clean-cache:
# Intentionally don't use "*" below... Avoid risk of accidentally running rm -rf /*
	test -n "@LOOLWSD_CACHEDIR@" && rm -rf "@LOOLWSD_CACHEDIR@"/[0-9a-f]
Autofooize 2015-03-09 04:11:15 -05:00			`bin_PROGRAMS = loolwsd`

Start on load testing Add a new program, loadtest, that runs a requested number of client sessions in parallel to a loolwsd server. A client session loads one of a list of test documents, and does some operations on it. Move the getTokenInteger() and getTokenString() functions out from LOOLSession into a new namespace LOOLProtocol, as they are neeeded also in the loadtest program. Add, also in LOOLProtocol, functions to parse some of the messages from the server. (In general that is done in client JavaScript code, of course; only for testing purposes needed in C++ code.) 2015-03-26 09:49:07 -05:00			`loolwsd_SOURCES = LOOLWSD.cpp LOOLSession.cpp TileCache.cpp Util.cpp LOOLProtocol.cpp`
Use separate child processes for LibreOfficeKit For now, each LOOL client has a separate child process (or none at all, if it has accessed only information found in the cache). This will obviously have to chnage to handle collaboration. Etc. The parent process talks the same Websocket protocol with the child processes. When there is a child process for a client, traffic from the client is forwarded as such to the child process and vice versa. 2015-03-17 18:56:15 -05:00
Remove the dead "migratory socket" stuff 2015-03-27 09:26:33 -05:00			`noinst_PROGRAMS = loadtest connect`
Start on load testing Add a new program, loadtest, that runs a requested number of client sessions in parallel to a loolwsd server. A client session loads one of a list of test documents, and does some operations on it. Move the getTokenInteger() and getTokenString() functions out from LOOLSession into a new namespace LOOLProtocol, as they are neeeded also in the loadtest program. Add, also in LOOLProtocol, functions to parse some of the messages from the server. (In general that is done in client JavaScript code, of course; only for testing purposes needed in C++ code.) 2015-03-26 09:49:07 -05:00
			`loadtest_SOURCES = LoadTest.cpp Util.cpp LOOLProtocol.cpp`
Intermediate commit of start on transporting sockets to child process Will be needed if we want loolwsd to run on Windows. Then we will have one process receiving the connections from WebSocket clients and sending the accepted connection sockets to child processes thatr might be already running, either because they have been "pre-forked", or because of a collaboration scenario where new clients join a session working on a document. But initially we will write this as if for Unix only, so development of this migratory socket stuff is paused for now. (And it isn't even clear whether the API design so far is a good idea and elegantly implementable.) 2015-03-16 05:25:47 -05:00
Add trivial test program for sending commands to the LOOL server 2015-03-27 09:23:20 -05:00			`connect_SOURCES = Connect.cpp Util.cpp`

Use separate child processes for LibreOfficeKit For now, each LOOL client has a separate child process (or none at all, if it has accessed only information found in the cache). This will obviously have to chnage to handle collaboration. Etc. The parent process talks the same Websocket protocol with the child processes. When there is a child process for a client, traffic from the client is forwarded as such to the child process and vice versa. 2015-03-17 18:56:15 -05:00			`clean-cache:`
			`# Intentionally don't use "" below... Avoid risk of accidentally running rm -rf /`
Do remove also the first level of subdirectories 2015-03-27 07:52:30 -05:00			`test -n "@LOOLWSD_CACHEDIR@" && rm -rf "@LOOLWSD_CACHEDIR@"/[0-9a-f]`