3 ms·
Approximately: because browsers already have good HTTP parsers built in, and that seems safer than trying a new fast binary parser.
by brians 7y ago
Approximately: because browsers already have good HTTP parsers built in, and that seems safer than trying a new fast binary parser.
- cheez 7y agoFair enough.
- mehrdadn 7y agoIs performance really such a big concern here? How slowly can one possibly parse binary DNS responses in a native language?
- jbverschoor 7y agoAlso, why a complete http stack? Before we know it we need to send JSON packets to the cpu to do some multiplication