Lines Matching full:may

13 .\"    may be used to endorse or promote products derived from this software
66 messages may be lost or duplicated and may arrive out-of-order.
67 A datagram socket may send messages to and receive messages from multiple
76 Connection setup is required before data communication may begin.
81 Users of the last two abstractions may use the facilities for
89 Each socket may have a specific \fIprotocol\fP associated with it.
95 For example, within the ``Internet'' domain, the SOCK_DGRAM type may be
97 type may be implemented by the TCP transmission control protocol, while
102 Sockets may be \fIconnected\fP or \fIunconnected\fP.  An unconnected
110 The protocol may be given as 0, meaning any suitable protocol.
111 One of several possible protocols may be selected using identifiers
124 Such a binding may be established by a \fIbind\fP call:
129 Datagram sockets may have default bindings established when first
132 a socket's bound name may be retrieved with a \fIgetsockname\fP call:
142 Domains may support sockets with several names.
173 the \fIconnect\fP call may be used with such sockets
178 and asynchronous error reports may be received.
204 Messages may be sent from a socket by:
267 address if the socket is unconnected; \fImsg_name\fP may be given as
287 The normal UNIX \fIread\fP and \fIwrite\fP calls may be
290 received.  A process may operate on a virtual circuit socket, a terminal
312 Sockets, and their underlying communication protocols, may
313 support \fIoptions\fP.  These options may be used to manipulate
347 Socket names are strings and may appear in the UNIX file
352 this may change in future releases.
384 Options may be used to
388 The host part may optionally be interpreted as a subnet field