1 | /****************************************************************************
|
---|
2 | **
|
---|
3 | ** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies).
|
---|
4 | ** All rights reserved.
|
---|
5 | ** Contact: Nokia Corporation ([email protected])
|
---|
6 | **
|
---|
7 | ** This file is part of the documentation of the Qt Toolkit.
|
---|
8 | **
|
---|
9 | ** $QT_BEGIN_LICENSE:FDL$
|
---|
10 | ** Commercial Usage
|
---|
11 | ** Licensees holding valid Qt Commercial licenses may use this file in
|
---|
12 | ** accordance with the Qt Commercial License Agreement provided with the
|
---|
13 | ** Software or, alternatively, in accordance with the terms contained in a
|
---|
14 | ** written agreement between you and Nokia.
|
---|
15 | **
|
---|
16 | ** GNU Free Documentation License
|
---|
17 | ** Alternatively, this file may be used under the terms of the GNU Free
|
---|
18 | ** Documentation License version 1.3 as published by the Free Software
|
---|
19 | ** Foundation and appearing in the file included in the packaging of this
|
---|
20 | ** file.
|
---|
21 | **
|
---|
22 | ** If you have questions regarding the use of this file, please contact
|
---|
23 | ** Nokia at [email protected].
|
---|
24 | ** $QT_END_LICENSE$
|
---|
25 | **
|
---|
26 | ****************************************************************************/
|
---|
27 |
|
---|
28 | /*!
|
---|
29 | \page ipc.html
|
---|
30 | \title Inter-Process Communication in Qt
|
---|
31 | \brief Inter-Process communication in Qt applications.
|
---|
32 |
|
---|
33 | \ingroup technology-apis
|
---|
34 | \ingroup qt-basic-concepts
|
---|
35 | \ingroup qt-network
|
---|
36 |
|
---|
37 | Qt provides several ways to implement Inter-Process Communication
|
---|
38 | (IPC) in Qt applications.
|
---|
39 |
|
---|
40 | \section1 TCP/IP
|
---|
41 |
|
---|
42 | The cross-platform \l{QtNetwork} module provides classes that make
|
---|
43 | network programming portable and easy. It offers high-level
|
---|
44 | classes (e.g., QNetworkAccessManager, QFtp) that communicate using
|
---|
45 | specific application-level protocols, and lower-level classes
|
---|
46 | (e.g., QTcpSocket, QTcpServer, QSslSocket) for implementing
|
---|
47 | protocols.
|
---|
48 |
|
---|
49 | \section1 Shared Memory
|
---|
50 |
|
---|
51 | The cross-platform shared memory class, QSharedMemory, provides
|
---|
52 | access to the operating system's shared memory implementation.
|
---|
53 | It allows safe access to shared memory segments by multiple threads
|
---|
54 | and processes. Additionally, QSystemSemaphore can be used to control
|
---|
55 | access to resources shared by the system, as well as to communicate
|
---|
56 | between processes.
|
---|
57 |
|
---|
58 | \section1 D-Bus
|
---|
59 |
|
---|
60 | The \l{QtDBus} module is a Unix-only library you can use to
|
---|
61 | implement IPC using the D-Bus protocol. It extends Qt's
|
---|
62 | \l{signalsandslots.html} {Signals and Slots} mechanism to the IPC
|
---|
63 | level, allowing a signal emitted by one process to be connected to
|
---|
64 | a slot in another process. This \l {D-Bus} page has detailed
|
---|
65 | information on how to use the \l{QtDBus} module.
|
---|
66 |
|
---|
67 | \section1 Qt COmmunications Protocol (QCOP)
|
---|
68 |
|
---|
69 | The QCopChannel class implements a protocol for transferring messages
|
---|
70 | between client processes across named channels. QCopChannel is
|
---|
71 | only available in \l{Qt for Embedded Linux}. Like the \l{QtDBus}
|
---|
72 | module, QCOP extends Qt's \l{Signals and Slots} mechanism to the
|
---|
73 | IPC level, allowing a signal emitted by one process to be
|
---|
74 | connected to a slot in another process, but unlike QtDBus, QCOP
|
---|
75 | does not depend on a third party library.
|
---|
76 | */
|
---|