From e97a1e6b1061a5ea0d483529fea9a7f73611d1fd Mon Sep 17 00:00:00 2001 From: Itay Grudev Date: Tue, 9 Jun 2015 17:37:39 +0300 Subject: [PATCH] Updated implementation description --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7003edb..87d08ba 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ Usage ----- The ```SingleApplication``` class inherits from ```QApplication```. Use it as if you are using the ```QApplication``` class. -The library uses your ```Organization Name``` and ```Application Name``` to set up a Local Socket. The first instance of your Application would start a ```QLocalServer``` and then listen for connections on the socket. Every subsequent instance of your application would attempt to connect to that socket. If successful it will be terminated, while in the Primary Instance, ```SingleApplication``` would emmit the ```showUp()``` signal. +The library uses your ```Organization Name``` and ```Application Name``` to set up a ```QLocalServer``` and a ```QSharedMemory``` block. The first instance of your Application would check if the shared memory block exists and if not it will start a ```QLocalServer``` and then listen for connections on it. Each subsequent instance of your application would check if the shared memory block exists and if it does, it will connect to the QLocalServer to notify it that a new instance had been started, after which would terminate the new instance with status code ```0```. The Primary Instance, ```SingleApplication``` would emmit the ```showUp()``` signal upon detecting that a new instance had been started. The library uses ```stdlib``` to terminate the program with the ```exit()``` function. @@ -54,7 +54,7 @@ Implementation -------------- The library is implemented with a QSharedMemory block which is thread safe and guarantees a race condition will not occur. It also uses a QLocalSocket to notify the main process that a new instance had been spawned and thus invoke the ```showUp()``` signal. -To handle an issue with Unix systems, where the operating system owns the shared memory block and if the program crashes the memory remains untouched, the library binds to the following signals and closes the program with error code = ```128 + signum``` where signum is the number representation of the signal listed below. +To handle an issue with ```Unix``` systems, where the operating system owns the shared memory block and if the program crashes the memory remains untouched, the library binds to the following signals and closes the program with error code = ```128 + signum``` where signum is the number representation of the signal listed below. Handling the signal is required in order to safely delete the ```QSharedMemory``` block. * ```SIGINT ``` - ```2``` * ```SIGILL ``` - ```4```