Skip to content
Category

Inter-process communication

page 1
computer file
contained block of information on a computer
AJAX
group of interrelated Web development techniques
client-server model
distributed application structure in computing
FIFO
scheduling algorithm
inter-process communication
mechanisms an operating system provides to allow the processes to manage shared data
Common Object Request Broker Architecture
standard to facilitate communication between systems on diverse platforms
broadcasting
network messaging to multiple recipients simultaneously
Server Message Block
network communication protocol for providing shared access to resources
RPC
mechanism to allow software to execute a remote procedure
Component Object Model
Application Binary Interface by Microsoft
D-Bus
D-Bus (short for "Desktop Bus"
signal
form of inter-process communication in computer systems
shared memory
memory that may be simultaneously accessed by multiple programs with an intent to provide communication among them or avoid redundant copies
message passing
mechanism for interprocess communication
Object Linking and Embedding
technology developed by Microsoft
tee
standard UNIX utility
Network Information Service
client–server directory service protocol for distributing system configuration data such as user and host names between computers on a computer network, developed by Sun Microsystems
Parallel Virtual Machine
software tool for parallel networking of computers
message queue
means of interprocess communication in software engineering
named pipe
computing pipe which is accessible as a filesystem object
Advanced Message Queuing Protocol
computer network protocol
software pipeline
chain of processing software elements
Distributed Component Object Model
software for communication between software components
stream
sequence of data elements made available over time
Dynamic Data Exchange
inter-process communication protocol on Microsoft Windows
shell pipeline
set of Unix processes chained by their standard streams
Apache Thrift
data serialization format
Distributed Computing Environment
communications protocol
future
in concurrent programming, an object serves as a placeholder for a result that is initially unknown because the computation is incomplete (such an object is crucial in representing the final result during ongoing or not-yet-started computations)
Bonobo (GNOME)
component framework for the GNOME free desktop environment
mmap
In computing, mmap(2) is a POSIX-compliant Unix system call that maps files or devices into memory. It is a method of memory-mapped file I/O. It implements demand paging because file contents are not immediately read from disk and initially use no physical RAM at all. The actual reads from disk are performed after a specific location is accessed, in a lazy manner. After the mapping is no longer needed, the pointers must be unmapped with munmap(2). Protection information—for example, marking mapped regions as executable—can be managed using mprotect(2), and special treatment can be enforced usi
anonymous pipe
transient computing pipe constructed as part of a shell pipeline
9P
Plan 9 filesystem protocol
ARexx
ARexx is a Rexx interpreter for Amiga, written in 1987 by William S. Hawes, with a number of Amiga-specific features beyond standard Rexx. An ARexx script can communicate with software that implements an ARexx port. An Amiga application can define a set of commands and functions for ARexx to address, thus making the capabilities of the software available to an ARexx script. Several applications support running an ARexx script as a macro.
Amazon Simple Queue Service
service offered by Amazon Web Services
Inter-Client Communication Conventions Manual
standard for interoperability between X Window System clients of the same X server.
Apache Avro
Apache Avro™ is a data serialization system.
ZeroMQ
ZeroMQ (also spelled ØMQ, 0MQ or ZMQ) is an asynchronous messaging library, aimed at use in distributed or concurrent applications. It provides a message queue, but unlike message-oriented middleware, a ZeroMQ system can run without a dedicated message broker; the zero in the name is for "zero broker". The library's API is designed to resemble Berkeley sockets.
messaging pattern
any architectural pattern that describes communication between software systems or subsystems
Microsoft Transaction Server
Software
Internet Communications Engine
computer software middleware platform developed by ZeroC
computer network programming
writing computer programs with networking capability
Celery
distributed task queue
channel
model for interprocess communication and synchronization via message passing
traffic flow
sequence of packets from a source computer to a destination, which may be another host, a multicast group, or a broadcast domain