Maybe a bit too MS/OO specific. Describing the server activity in pseudo code would leave the reader with some understanding of how various simple and scaling options can be added in: inr st a time, all in one executive thread, multi-process, multi-thread, redirect to other servers, dns load spreading. Describing how one protocol runs on top of another is a bit light: behavior rules and message formats. Lack of thumbnail TCP overview seemed strange, not to mention IP and DNS. HTTP/1.1 is a bit extra confusing, as it has so many new bells and whistles.
Still, a good description of many aspects.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Maybe a bit too MS/OO specific. Describing the server activity in pseudo code would leave the reader with some understanding of how various simple and scaling options can be added in: inr st a time, all in one executive thread, multi-process, multi-thread, redirect to other servers, dns load spreading. Describing how one protocol runs on top of another is a bit light: behavior rules and message formats. Lack of thumbnail TCP overview seemed strange, not to mention IP and DNS. HTTP/1.1 is a bit extra confusing, as it has so many new bells and whistles.
Still, a good description of many aspects.