How do I speak { HTTP, POP3, SMTP, FTP, Telnet, NNTP, etc. } with Winsock?
Winsock proper does not provide a way for you to speak these protocols, because it only deals with the layers underneath these application-level protocols. However, there are many ways for you to get your program to speak these protocols. The easiest method is to use a third-party library. The Resources section lists several of these. If you only need to speak the HTTP, FTP or gopher protocols, you can use the WinInet library exposed by Microsoft’s Internet Explorer. Newer versions of Microsoft’s development tools include components that make accessing WinInet simple. Finally, you can always roll your own. You should start by reading the specification for the protocol you want to implement. Most of the Internet’s protocols are documented in RFCs. The Important RFCs page links to the most commonly referenced application-level RFCs. The complexity of the protocols vary widely, and the only way to gauge the difficulty of implementing the protocol is to read the relevant RFC(s). HTTP, for
Related Questions
- There are HTTP Slow Response, FTP Slow Response, SMTP Slow Response and POP3 Slow Response in the diagnoses events when I run Colasoft Capsa. Whats wrong and does it severe?
- Can I use all the Internet protocols (FTP, telnet, SMTP, POP3, Messenger), etc.?
- How do I speak { HTTP, POP3, SMTP, FTP, Telnet, NNTP, etc. } with Winsock?
