Sockets are another method of interprocess communication. One of the primary features of sockets are that they can be used to communicate between processes on different machines using a TCP/IP network connection.
A portable standard for network application providers on TCP/IP networks.
Also commonly known as Unix Berkeley Sockets, these were developed in the early 1980s as a means of providing application writers a portable means of accessing the communications hardware of the network. Since sockets allow point to point communications between processes, it is used in most of the networked workstation implementations of message passing libraries.
Specifies the end points of a two-way communications channel that connects two processes together so they can exchange information.
IBM term for software interfaces that allow two Unix application programs to talk via TCP/IP protocols.
In UNIX and some other operating systems, a software object that connects an application to a network protocol. In UNIX, for example, a program can send and receive TCP/IP messages by opening a socket and reading and writing data to and from the socket. This simplifies program development because the programmer need only worry about manipulating the socket and can rely on the operating system to actually transport messages across the network correctly.
Sockets are a method for communication between a client program and a server program over a network. A socket is defined as "the endpoint in a connection." Sockets are created and used with a set of programming requests or "function calls" sometimes called the sockets application programming interface (API).
A name given to the package of sub-routines that provide access to TCP/IP on most systems.
An API (Application Program Interface) for communications between Unix & TCP/IP.
A programming method for connecting applications across a network. Used by Web applications as a way to access databases. See also ODBC, JDBC