New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move client code used by server code down into proto #1879
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. I think it would be good to make the txt parsing portion of the library a default off feature. The resolver generally does not need any of that code, and I think it's enough that it probably makes a difference.
We could call it text-parsing
or something like that?
a73907f
to
8c7b85d
Compare
@djc take a look at my recent changes... I also fixed all the current cleanliness issues, separate commits. |
Sorry for losing sight of this, LGTM (I can't merge it since I'm the author). |
I'm going to rebase and then merge... thanks @djc |
b4932cb
to
a35f331
Compare
All the low-level stuff in the client code was quite generic (and in fact used by the server).
As a future improvement, we might move all the networking stuff out of -proto into a trust-dns-net crate maybe? It would be nice if trust-dns-proto was sans-io.