3 ms·
// DNS Header // raw[0:1] ID of the query // raw[2] // bit 0 - QR // bit 1:4 - OPCODE etc Easier to write and possibly to read.
by raverbashing 12y ago
// DNS Header
// raw[0:1] ID of the query
// raw[2]
// bit 0 - QR
// bit 1:4 - OPCODE
etc
Easier to write and possibly to read.
- sbilstein 12y agoYea definitely, this engineer should deviate from very standard looking easy to visualize format./s Take a look at this RFC defining websockets written in 2011 http://tools.ietf.org/html/rfc6455#section-5.2 http://tools.ietf.org/html/rfc6455#section-5.2 and the RFC for TCP from 1981 (check out section 3.1 describing the header) http://www.ietf.org/rfc/rfc793.txt http://www.ietf.org/rfc/rfc793.txt See the similarity? We have over 30 years of consistency here.