![]() ![]() ![]() ![]() Tip 29: Don’t Hardcode IP Addresses or Port Numbers in Your Application. Tip 27: Zero the sockaddr_in Structure Before Use. Tip 25: Understand How to Time Out a connect Call. Tip 24: When Possible, Use One Large Write Instead of Multiple Small Writes. Tip 23: Servers Should Set the SO_REUSEADDR Option. Tip 22: Don’t Use TIME-WAIT Assassination to Close a Connection. Tip 21: Consider Making Your Applications Event Driven (2). Tip 20: Consider Making Your Applications Event Driven (1). Tip 19: Consider Using Two TCP Connections. Tip 18: Consider Letting tcpmux ‘‘Assign’’ Your Server’s Well-known Port. Tip 17: Consider Letting inetd Launch Your Application. Tip 16: Understand the TCP Orderly Release Operation. Tip 15: Understand the TCP Write Operation. Tip 14: Don’t Take the OSI Seven-Layer Reference Model Too Seriously. Tip 12: Don’t Assume That a Successful LAN Strategy Will Scale to a WAN. Tip 11: Be Prepared for Rude Behavior from a Peer. Tip 10: Remember That TCP/IP Is Not Polled. Tip 9: Realize That TCP Is a Reliable Protocol, Not an Infallible Protocol. Tip 7: Don’t Underestimate the Performance of TCP. Tip 6: Remember That TCP Is a Stream Protocol. Tip 5: Prefer the Sockets Interface to XTI/TLI. Tip 4: Develop and Use Application ‘‘Skeletons’’. Tip 3: Understand Private Addresses and NAT. Tip 1: Understand the Difference between Connected and Connectionless Protocols. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |