BREAKING CHANGE: slog: {r => dnsR}aw{Query,Response} #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Explicitly scope the rawQuery and rawResponse, which are not general fields but specific of the DNS. This should make it more intuitive to auto-generate a tabular format.
bassosimone
added a commit
to rbmk-project/rbmk-project.github.io
that referenced
this pull request
Nov 29, 2024
bassosimone
added a commit
to rbmk-project/rbmk-project.github.io
that referenced
this pull request
Nov 29, 2024
bassosimone
added a commit
to rbmk-project/x
that referenced
this pull request
Nov 29, 2024
1. `domain` => `dnsLookupDomain` 2. `addrs` => `dnsResolvedAddrs` 3. `count` => `ioBufferSize` or `ioBufferCount` This set of changes is part of an overall effort to ensure it's relatively trivial to serialize to a flat data format. To this end, figure out which fields are really common and which fields, instead, are specific, and add prefixes to the specific ones to make it very clear what they are about. Also, avoid overload, and split into two fields when we're using the same field with two distinct semantics dependent on the message type. This should also increase the data format orthogonality. See also rbmk-project/dnscore#13
bassosimone
added a commit
to rbmk-project/x
that referenced
this pull request
Nov 29, 2024
1. `domain` => `dnsLookupDomain` 2. `addrs` => `dnsResolvedAddrs` 3. `count` => `ioBufferSize` or `ioBufferCount` This set of changes is part of an overall effort to ensure it's relatively trivial to serialize to a flat data format. To this end, figure out which fields are really common and which fields, instead, are specific, and add prefixes to the specific ones to make it very clear what they are about. Also, avoid overload, and split into two fields when we're using the same field with two distinct semantics dependent on the message type. This should also increase the data format orthogonality. See also rbmk-project/dnscore#13 While there, bump the `rbmk-project/{common,dnscore}` dependencies.
bassosimone
added a commit
to rbmk-project/rbmk
that referenced
this pull request
Nov 29, 2024
bassosimone
added a commit
to rbmk-project/rbmk
that referenced
this pull request
Nov 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explicitly scope the rawQuery and rawResponse, which are not general fields but specific of the DNS. This should make it more intuitive to auto-generate a tabular format.
While there, upgrade to
rbmk-project/common v0.4.0.