Lines Matching full:sockets

59 demonstrate in a simple way the use of pipes, socketpairs, sockets
166 The descriptors can represent open files or sockets (sockets are communication
199 mechanism with two ends, or sockets.  Data that is written into one socket
228 This routine creates a pipe and places descriptors for the sockets
232 sockets it created.
278 pair of connected sockets for one-way stream communication.  One may
279 obtain a pair of connected sockets for two-way stream communication
296 to sockets and implies certain other conventions.
299 The UNIX domain uses UNIX path names for naming sockets.  
301 between sockets on the same machine.
336 We would like to have two processes separately create sockets
340 In Berkeley UNIX 4.4BSD one can create individual sockets, give them names and
343 Sockets created by different programs use names to refer to one another;
347 There are several domains for sockets.
367 place across a connection between two sockets.  The communication
402 keeps track of the names that are bound to sockets,
403 sets up connections and	transfers data between sockets,
405 This code also keeps track of the names that are bound to sockets.
428 Let us now look at two programs that create sockets separately.
431 The structure used to name UNIX domain sockets is defined
436 These sockets are in the UNIX domain.
467 contrast with the Internet domain, unbound sockets need not be (and are
474 one can send the names of additional, perhaps new, sockets over the link.
508 of a pair of communicating sockets.
512 An association may be transient when using datagram sockets;
579 To send data between stream sockets (having communication style SOCK_STREAM),
580 the sockets must be connected.
675 sockets before another connection request.
720 both files and sockets.  These are \fIreadv()\fP and \fI writev(),\fP
741 These calls are used only with sockets; specifying a descriptor for a file will
880 creating and naming sockets	socket(2), bind(2)