Skip to content
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

Do not require redundant REUSE_ENTRY command #4

Open
dtikhonov opened this issue Dec 7, 2017 · 0 comments
Open

Do not require redundant REUSE_ENTRY command #4

dtikhonov opened this issue Dec 7, 2017 · 0 comments
Milestone

Comments

@dtikhonov
Copy link

Section 7.1.1 of the first draft states that

If the encoded name component refers to an existing entry, this entry is reused as described in Section 7.1.2.

This is a wasted byte. The reuse of existing entry in this case is implied and should be inferred by the decoder.

@litespeedtech litespeedtech added this to the Second Draft milestone Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants