diff options
Diffstat (limited to 'src/corelib/doc/src/ipc.qdoc')
| -rw-r--r-- | src/corelib/doc/src/ipc.qdoc | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/src/corelib/doc/src/ipc.qdoc b/src/corelib/doc/src/ipc.qdoc index 1de20f89a2..7ec6f5fa3b 100644 --- a/src/corelib/doc/src/ipc.qdoc +++ b/src/corelib/doc/src/ipc.qdoc @@ -7,6 +7,7 @@ \ingroup groups \ingroup frameworks-technologies \keyword ipc + \ingroup explanations-networkingandconnectivity \brief An overview of Qt's inter-process communication functionality @@ -85,7 +86,7 @@ \keyword ipc \keyword shared memory - \brief Overview of the techniques for sharing memory between processes + \brief Overview of the techniques for sharing memory between processes. Qt provides two techniques to share memory with other processes in the same system: \l{QSharedMemory} and memory-mapped files using \l{QFile}. Memory @@ -273,7 +274,10 @@ file names, in particular those that separate path components (slash and backslash), with the exception of sandboxed applications on Apple operating systems. The following are good examples of cross-platform keys: "myapp", - "org.example.myapp", "org.example.myapp-12345". + "org.example.myapp", "org.example.myapp-12345". Note that it is up to the + caller to prevent oversized keys, and to ensure that the key contains legal + characters on the respective platform. Qt will silently truncate keys that + are too long. \b{Apple sandbox limitations:} if the application is running inside of a sandbox in an Apple operating system, the key must be in a very specific @@ -386,7 +390,7 @@ Qt's own build. For Windows systems, it was always the Windows backend. For Unix systems, it defaulted to the System V backend if the configuration script determined it was available. If it was not available, it fell back - to the POSIX one (since Qt 4.8). The POSIX backend could be explicitly + to the POSIX one. The POSIX backend could be explicitly selected using the \c{-feature-ipc_posix} option to the Qt configure script; if it was enabled, the \c{QT_POSIX_IPC} macro would be defined. @@ -410,7 +414,7 @@ It can be updated to be: \code QSharedMemory shm(QSharedMemory::legacyNativeKey("org.example.myapplication")); - QSystemSempahore sem(QSystemSemaphore::legacyNativeKey("org.example.myapplication")); + QSystemSemaphore sem(QSystemSemaphore::legacyNativeKey("org.example.myapplication")); \endcode If the two applications exchanged native keys, there is no need to update |