Fucking classic, i learned to program using these documents: https://github.com/therevoltingx/rootscan
Beej's Guide to Network Programming
11–20 of 51 posts
Re: Beej's Guide to Network Programming
#12If I'm not mistaken this original document was on Chico State's computer science domain. It was my understanding Beej went to Chico; does anyone know for sure? This was around long before 2006, I remember reading it around the year 2000 when I was first getting into C++. (miracle this quality of a document escaped anyone's brain in Chico -- I know, I went to CSUC. Let's just say it was hard to concentrate there :)
Re: Beej's Guide to Network Programming
#13If I'm not mistaken this original document was on Chico State's computer science domain. It was my understanding Beej went to Chico; does anyone know for sure? This was around long before 2006, I remember reading it around the year 2000 when I was first getting into C++. (miracle this quality of a document escaped anyone's brain in Chico -- I know, I went to CSUC. Let's just say it was hard to concentrate there :)
I also remember seeing this around the year 2000. (One giveaway that it's written in a previous century: It mentions SunOS. Not Solaris, but SunOS. When's the last time you heard somebody talk about that?) At that point I was already familiar with sockets, and mainly found the guide memorable because the name "Beej" had a weird sound to it.
Re: Beej's Guide to Network Programming
#14If I'm not mistaken this original document was on Chico State's computer science domain. It was my understanding Beej went to Chico; does anyone know for sure? This was around long before 2006, I remember reading it around the year 2000 when I was first getting into C++. (miracle this quality of a document escaped anyone's brain in Chico -- I know, I went to CSUC. Let's just say it was hard to concentrate there :)
He did indeed. Chico State's CSCI program was actually very good in the early 90s.
Re: Beej's Guide to Network Programming
#15this is indeed a great resource, but nothing can be considered as hackNEWS
Re: Beej's Guide to Network Programming
#16When I was at university I wanted to take a class that had 'introduction to computer networks' as a prerequisite, but I didn't want to wait 2 semesters for it to come around again after taking networks first. I spoke to the professor and he said he'd let me enroll in the course if I promised to carefully read Beej's guide first, since it contains all the essentials I'd really need for this follow-on. So, this saved me 6 months, what a golden nugget!
Re: Beej's Guide to Network Programming
#17Still refer to it every so often, especially as backup documentation from the man pages when something isn't entirely clear.
Re: Beej's Guide to Network Programming
#18This was an absolute lifesaver when I was thrown into the deep end writing a high-performance TCP server from scratch. I think it's so effective because it's "highly opinionated", which is to say, he points out "Foo does this, but don't use it because that's just silly" or "don't use bar, use baz instead because it handles qux more easily" and so on.
what makes this stuff seem "high-performance" TCP to you? This is standard socket programming. High performance TCP server is when you actually roll out your own TCP stack.
Re: Beej's Guide to Network Programming
#19A reference for beginners!
Re: Beej's Guide to Network Programming
#20Still not updated to mention anything more than select() as far as non-blocking IO is concerned, like poll, epoll, or, god no, using an abstract event loop. Nobody who cares about their code and sanity does blocking I/O with sockets.
But then, I must confess I too started network programming with this guide :) It presents the basics nicely, but there's a lot more you should learn about network programming.