3 ms·

I just put that I had worked with TCP/IP on a resume once, and they asked me what fields were in a TCP header. I was able to reconstruct all but one from first

I just put that I had worked with TCP/IP on a resume once, and they asked me what fields were in a TCP header. I was able to reconstruct all but one from first principles, since I didn't actually remember them all. If I'd put "10" in TCP/IP for that company, I would have been slammed in the interview. As it was I passed. Apparently no one ever remembers the CRC byte in the TCP header. :)

rdl 14y ago
People who have to worry about checksum offloading for high performance know this :) ... This is a feature of high end network cards. (although, in fairness, I'd only require that level of knowledge at the tip of tongue if someone was going to be a network stack developer or high level sysadmin/network admin -- for a regular web developer, just knowing that there are tcp headers and flags which can be set, and which might get mangled by devices between client and server, is enough. It's CRC at the level below TCP (well, 2 layers below: ethernet)