Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Justify keeping AliasForm and ServiceForm in one RR type, or split them into two #125
We've gotten multiple comments asking why AliasForm and ServiceForm aren't separate RR types. From a recursive resolver's perspective, this would simplify the processing logic. However, it would also result in double the QPS for everyone, since clients would have to fire off simultaneous queries for both Qtypes.
Actually, I think it's worse than double. A client, not knowing whether its recursive will perform special-case handling of these queries, has to issue both queries immediately. A recursive, upon seeing a ServiceForm query, would itself have to issue both ServiceForm and AliasForm queries, both at this point in the chain and subsequently at every point down the chain. So it somewhat more than doubles the load of the whole design, and the recursive behavior is possibly even more complex.