Thread: c network programming:insight on new books

  1. #1
    Registered User
    Join Date
    Dec 2011
    Posts
    1

    c network programming:insight on new books

    i'm currently doing some things in network programming but the book i use currently is internetworking with tcp\ip windows socket version....kind of think the book is obsolete tried google searching but all the books i found are in the early 2000's...can any one recommend anyone book that is a little 2007-2012 like......i'm sticking to c or cplusplus.....thnks 4 ur immediate reply

  2. #2
    Registered User
    Join Date
    Dec 2007
    Posts
    2,675
    Network programming in C has not changed much at all in a long time. Why do you think it's obsolete?

  3. #3
    Registered User ledow's Avatar
    Join Date
    Dec 2011
    Posts
    435
    Yes, unlike DirectX, or drivers, or any of the other interfaces that change every week, networking is pretty much locked in by design. You open a socket, send packets, act on packets received. About the only change that's happened in the last ten years is IPv6 (and even that's usually nothing more than using a slightly different function and new structures to hold information). Even back to the early days of Unix network programming, almost nothing has changed at all in networking.

    This is mainly, of course, due to the fact that networking has to talk the same to every computer on the planet. So although the drivers change, and the hardware speed changes, the actual method of communication CAN'T change without everyone changing everything. The TCP packets you sent 25 years ago are just as valid coming into a modern machine as they were then, even if all the hardware in between has changed radically.

    I don't know what people's obsession is with thinking that programming (especially in C) can get "out of date". If you can run the example programs given, it's still in-date and not obsolete.

    And this really belong in the "book" forum rather than here.

    - Compiler warnings are like "Bridge Out Ahead" warnings. DON'T just ignore them.
    - A compiler error is something SO stupid that the compiler genuinely can't carry on with its job. A compiler warning is the compiler saying "Well, that's bloody stupid but if you WANT to ignore me..." and carrying on.
    - The best debugging tool in the world is a bunch of printf()'s for everything important around the bits you think might be wrong.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Books (not specifically programming books)
    By DavidP in forum General Discussions
    Replies: 6
    Last Post: 11-05-2009, 07:33 PM
  2. Would anyone recommend good network security books?
    By donglee in forum Networking/Device Communication
    Replies: 1
    Last Post: 04-11-2009, 09:11 AM
  3. C programming books
    By Kurupt in forum C Programming
    Replies: 2
    Last Post: 11-11-2003, 12:53 PM
  4. Books on programming C++
    By Pooler in forum C++ Programming
    Replies: 20
    Last Post: 07-15-2003, 12:49 AM