libreoffice-online/loolwsd/Makefile.am

bin_PROGRAMS = loolwsd

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

# This code not actually used for now
MIGRATORY_SOCKET_SOURCES = MigratorySocket.cpp MigratorySocketTransport.cpp

noinst_PROGRAMS = sockettransporttest

sockettransporttest_SOURCES = SocketTransportTest.cpp $(MIGRATORY_SOCKET_SOURCES)

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`

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			`loolwsd_SOURCES = LOOLWSD.cpp LOOLSession.cpp TileCache.cpp Util.cpp`

			`# This code not actually used for now`
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			`MIGRATORY_SOCKET_SOURCES = MigratorySocket.cpp MigratorySocketTransport.cpp`

			`noinst_PROGRAMS = sockettransporttest`

			`sockettransporttest_SOURCES = SocketTransportTest.cpp $(MIGRATORY_SOCKET_SOURCES)`

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 /`
			`test -n "@LOOLWSD_CACHEDIR@" && rm -rf "@LOOLWSD_CACHEDIR@"/[0-9a-f]/*`