socket

一. AF 和 PF

    作为宏定义，两者对应的数值完全相同，区别只存在于文字上：

        AF: Address  Family

        PF: Protocol Family

    特别说明，在 Unix/Linux 系统的不同版本中，这两者存在微小差别，对于 BSD 是 AF，对于 POSIX 是 PF。

    注: 理论上，创建 socket 是指定协议，应用 PF_xxxx，而设置地址应用 AF_xxxx。但 man socket 出现的都是 AF，故建议统一用 AF。

二. socket

        int socket(int domain, int type, int protocol);

    creates an endpoint for communication and returns a descriptor.

    The domain argument specifies a communication domain; this selects the protocol family which will be used for communication. These families are defined in <sys/socket.h>. The currently understood formats include:

       Name                Purpose                          Man page
       AF_UNIX, AF_LOCAL   Local communication              unix(7)
       AF_INET             IPv4 Internet protocols          ip(7)
       AF_INET6            IPv6 Internet protocols          ipv6(7)
       AF_IPX              IPX - Novell protocols
       AF_NETLINK          Kernel user interface device     netlink(7)
       AF_X25              ITU-T X.25 / ISO-8208 protocol   x25(7)
       AF_AX25             Amateur radio AX.25 protocol
       AF_ATMPVC           Access to raw ATM PVCs
       AF_APPLETALK        Appletalk                        ddp(7)
       AF_PACKET           Low level packet interface       packet(7)

    The socket has the indicated type, which specifies the communication semantics.  Currently defined types are:

        SOCK_STREAM     Provides sequenced, reliable, two-way, connection-based byte streams.  An out-of-band data  transmission  mechanism may be supported.
        SOCK_DGRAM      Supports datagrams (connectionless, unreliable messages of a fixed maximum length).
        SOCK_SEQPACKET  Provides  a  sequenced,  reliable,  two-way  connection-based data transmission path for datagrams of fixed maximum length; a consumer is required to read an entire packet with each input system call.
        SOCK_RAW        Provides raw network protocol access.
        SOCK_RDM        Provides a reliable datagram layer that does not guarantee ordering.
        SOCK_PACKET     Obsolete and should not be used in new programs; see packet(7).
    Some socket types may not be implemented by all protocol families; for example, SOCK_SEQPACKET is not implemented for AF_INET.
    Since Linux 2.6.27, the type argument serves a second purpose: in addition to specifying a socket type, it may include the  bitwise OR of any of the following values, to modify the behavior of socket():
       SOCK_NONBLOCK   Set  the  O_NONBLOCK  file  status  flag  on  the  new open file description.  Using this flag saves extra calls to fcntl(2) to achieve the same result.
       SOCK_CLOEXEC    Set the close-on-exec (FD_CLOEXEC) flag on the new file descriptor.  See the description of the O_CLOEXEC  flag  in open(2) for reasons why this may be useful. 当子进程 exec 一个新的程序时，调用进程中打开的文件描述符仍然保持打开，但设置了执行即关 FD_CLOEXEC 的文件描述字除外。

    The protocol specifies a particular protocol to be used with the socket.  Normally only a single protocol exists to support a par‐ticular socket type within a given protocol family, in which case protocol can be specified as 0.  However,  it  is  possible  that many protocols may exist, in which case a particular protocol must be specified in this manner.  The protocol number to use is spe‐cific to the “communication domain” in which communication is to take place; see protocols(5).  See getprotoent(3) on  how  to  map protocol name strings to protocol numbers.
    Sockets of type SOCK_STREAM are full-duplex byte streams, similar to pipes(PS: PIPES are not full-duplex).  They do not preserve record boundaries.  A stream socket must be in a connected state before any data may be sent or received on it.  A connection to another socket is created  with a  connect(2)  call.   Once  connected, data may be transferred using read(2) and write(2) calls or some variant of the send(2) and recv(2) calls.  When a session has been completed a close(2) may be  performed.   Out-of-band  data  may  also  be  transmitted  as described in send(2) and received as described in recv(2).

    Q: what's the differences between read/write and send/recv? 

    A: http://blog.csdn.net/deng529828/article/details/6245254

三. raw socket

    利用 raw socket，可以在用户空间实现新的 IPv4 协议。raw socket 收发的报文不包含链路头，即硬件地址。