| /external/bison/lib/ |
| getopt_.h | 108 /* For communication from `getopt' to the caller.
117 This is used for communication to and from the caller
118 and for communication between successive calls to `getopt'.
|
| /hardware/ril/mock-ril/src/cpp/ |
| msgheader.pb.h | 28 namespace communication { namespace
121 // @@protoc_insertion_point(class_scope:communication.MsgHeader)
224 } // namespace communication
|
| /ndk/sources/host-tools/sed-4.2.1/lib/ |
| getopt.in.h | 107 /* For communication from `getopt' to the caller.
116 This is used for communication to and from the caller
117 and for communication between successive calls to `getopt'.
|
| /external/apache-http/src/org/apache/http/client/ |
| package.html | 37 The API for client-side HTTP communication and
|
| /external/bluetooth/bluez/tools/ |
| bccmd.8 | 21 Specify the communication transport. Valid options are:
|
| /external/clang/www/ |
| menu.html.incl | 34 <label>Communication</label>
|
| /external/e2fsprogs/lib/uuid/ |
| uuid.3.in | 47 web servers without communication between the servers, and without fear
|
| /external/iproute2/include/linux/ |
| netdevice.h | 4 * interface as the means of communication with the user level.
|
| /external/kernel-headers/original/linux/ |
| icmp.h | 4 * interface as the means of communication with the user level.
|
| ip.h | 4 * interface as the means of communication with the user level.
|
| /external/webkit/Source/WebCore/platform/chromium/ |
| ReadableDataObject.h | 43 // Used for one way communication of drag/drop and copy/paste data from the
|
| /frameworks/base/services/input/ |
| InputManager.h | 49 * internal state. Moreover, all communication is done one way from the InputReaderThread
|
| /frameworks/base/telephony/java/com/android/internal/telephony/cat/ |
| AppInterface.java | 20 * Interface for communication between STK App and CAT Telephony
|
| /prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/ |
| coda_psdev.h | 11 /* communication pending/processing queues */
|
| connector.h | 37 #define CN_W1_IDX 0x3 /* w1 communication */
|
| icmp.h | 4 * interface as the means of communication with the user level.
|
| if_tr.h | 4 * interface as the means of communication with the user level.
|
| sdla.h | 4 * interface as the means of communication with the user level.
|
| /external/chromium/chrome/common/ |
| devtools_messages.h | 19 // Chain of communication between the components may be described by the
104 // will handle communication with inspected page DevToolsAgent.
|
| /external/oprofile/doc/ |
| oprofile.1.in | 163 The device files for communication with the Linux 2.4 kernel module.
166 The device filesystem for communication with the Linux 2.6 kernel module.
|
| /frameworks/base/docs/html/sdk/ |
| android-2.3-highlights.jd | 170 communication (NFC) tags. For example, the user can ?touch? or ?swipe? an NFC
174 whose URL is included in the tag data. NFC communication relies on wireless
201 <li><a href="#communication">New forms of communication</a></li>
315 <h3 id="communication">New forms of communication</h3>
323 voice calls, without having to manage sessions, transport-level communication,
348 <p>NFC communication relies on wireless technology in the device hardware, so
|
| /frameworks/base/libs/ui/tests/ |
| InputChannel_test.cpp | 106 // Server->Client communication
115 // Client->Server communication
|
| /hardware/invensense/mlsdk/mllite/ |
| mldmp.c | 64 * communication.
235 * Does not close the serial communication. To do that,
|
| /external/dbus/doc/ |
| dbus-faq.xml | 46 Phrased differently, D-Bus is 1) an interprocess communication (IPC) system and 2) some higher-level
184 Interprocess communication system or wire protocol
215 A third, unrelated feature is interprocess communication or IPC.
249 benchmark, D-Bus one-to-one communication was about 2.5x slower than
255 D-Bus communication with the intermediate bus daemon should be
271 enable asynchronous communication and avoid round trips.
301 How does D-Bus differ from other interprocess communication
|
| dcop-howto.txt | 18 communication between KDE applications. KDE already has an extremely
85 To actually enable DCOP communication to begin, you must use
147 The return value of send() indicates whether DCOP communication succeeded
161 communication was successful.
455 of inter-process communication with KDE! Please direct all comments
460 Inter-user communication
491 NOTE: DCOP communication is not encrypted, so please do not
|
