TCP and UDP provide the platform for most other protocols like FTP, SMTP, and RDP, which operate at higher levels. TCP and UDP are transport protocols that define how data gets from place to place but don’t really care about what the data is. Sockets usually still use TCP or UDP, as they aren’t anything special other than a fancy pipe within the kernel. There are also raw sockets, which don’t have any restrictions, and are used for implementing different protocols and utilities that need to inspect low-level network traffic, like Wireshark. UDP-based sockets are datagram sockets, where order (or even delivery) isn’t guaranteed. TCP-based sockets are called stream sockets, where all data will arrive in order. Sockets simply provide the actual hardware for moving data around. This file doesn’t contain anything, and you shouldn’t modify it directly, except for the permissions where applicable. For example, MySQL’s socket is usually at: /var/lib/mysql/mysql.sock Instead, all the data is retained within kernel memory the only point of the socket file is to maintain a reference to the socket, and to give it filesystem permissions to control access. Despite creating files on disk, Unix sockets don’t actually write the data they send to the disk, as that would be far too slow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |