Useful Links And Good Books

[Hammer]

Here's a list of some of the web sites I've bookmarked that might be of interest to you. Also, I'll mention a couple of books I recommend reading.

Links:
What is a Socket? (http://whatis.techtarget.com/definition/0,,sid9_gci213021,00.html)
Beej's Guide to Network Programming Using Internet Sockets (http://beej.us/guide/bgnet/)
Unix Socket FAQ (http://www.developerweb.net/sock-faq/)
TCP/IP FAQ (http://www.faqs.org/faqs/internet/tcp-ip/tcp-ip-faq/)
Winsock Programmers FAQ (http://tangentsoft.net/wskfaq/)
TCP/IP Resource List (http://www.private.org.il/tcpip_rl.html)
Sockets.com (http://www.sockets.com/)
SockAddr.com (http://www.sockaddr.com/)
FTP RFC 959 (http://www.w3.org/Protocols/rfc959/)
SMTP RFC 821 (http://www.faqs.org/rfcs/rfc821.html)
Richard Stevens Homepage (http://www.kohala.com/start/)
Internet Assigned Numbers Authority (http://www.iana.org/)
American Registry For Internet Numbers (http://www.arin.net/)

Books:
Effective TCP/IP Programming by Jon Snader (http://pw1.netcom.com/~jsnader/)
Various books by Richard Stevens (http://www.kohala.com/start/#books)

Feel free to add yours to this thread, if its popular enough, I'll make it a sticky.

[Leeman_s]

I think everyone should first visit this website:

www.learntosubnet.com

[planet_abhi]

Good site thank you .

[Hammer]

Threads merged...

[devour89]

I learned it from: http://www.madwizard.org

Even though his tutorial isn't finished yet, its been a great explenation for me

[johnnie2]

I'd like to suggest:

Johnnie's Winsock Tutorial (http://www.hal-pc.org/~johnnie2/winsock.html)

for inclusion into the list.

[Salem]

Avoid the following Fallacies (http://blogs.sun.com/jag/resource/Fallacies.html) in your network programs


The Eight Fallacies of Distributed Computing

Essentially everyone, when they first build a distributed application, makes the following eight assumptions. All prove to be false in the long run and all cause big trouble and painful learning experiences.
1. The network is reliable
2. Latency is zero
3. Bandwidth is infinite
4. The network is secure
5. Topology doesn't change
6. There is one administrator
7. Transport cost is zero
8. The network is homogeneous
For more details, read the article by Arnon Rotem-Gal-Oz

[Salem]

Network analyser - http://www.ethereal.com/
Use this to
1. Watch what existing browser / email / ftp / chat client does already
2. Watch what your program is doing different, if you're writing a browser / email / etc

In a similar (or perhaps even the same vein), there's Wireshark (http://www.wireshark.org/), which is either the new name for ethereal, or a fork (I don't know which).

[Devil Panther]

there is one very important thing missing from this list, a raw sockets guide:
http://packetstorm.widexs.nl/programming-tutorials/raw_socket.txt


you gotta love raw sockets, even if win xp sp2 (*cough* lame *cough*) does not!

[Hammer]

Reading data from a socket (http://faq.cprogramming.com/cgi-bin/smartfaq.cgi?answer=1108255660&id=1044780608)

[Thantos]

FYI: The Beej guide has moved to http://beej.us/guide/bgnet/ and has been updated in the first post.

[NogginTheNog]

DevilPanther's link for raw sockets seems to be down/out-of-date, Try:

http://www.megasecurity.org/Programming/rawip.txt

[Devil Panther]

Here is a better document on Raw Sockets: http://www.madchat.org//coding/c/c.rezo/rawsckt/raw_socket.txt

[stuccio]

I think everyone should first visit this website:

www.learntosubnet.com

This, I'm sure, is a good tutorial but for windows dudes only ....
At least I can't get it to run under GNU\LINUX distro (at least true to the open source philosophy)

[Devil Panther]

This, I'm sure, is a good tutorial but for windows dudes only ....
At least I can't get it to run under GNU\LINUX distro (at least true to the open source philosophy)

I believe that anyone who ever dreams to write a network application should know NETWORKING!
But the link has nothing to do with Window or Linux, it's the general idea of how it works.

[Devil Panther]

Network analyser - http://www.ethereal.com/
Use this to
1. Watch what existing browser / email / ftp / chat client does already
2. Watch what your program is doing different, if you're writing a browser / email / etc


Ethereal is DEAD. :(
Well, not really... The name has changed, it's now called WireShark: http://www.wireshark.org/