Skip to content

Don't rely on the HTTP/1.1 Messaging specification to define "message"#344

Merged
mnot merged 2 commits intomasterfrom
mnot-311
Apr 27, 2020
Merged

Don't rely on the HTTP/1.1 Messaging specification to define "message"#344
mnot merged 2 commits intomasterfrom
mnot-311

Conversation

@mnot
Copy link
Copy Markdown
Member

@mnot mnot commented Mar 20, 2020

Fixes #311

@mnot mnot requested review from reschke and royfielding March 20, 2020 04:42
@MikeBishop
Copy link
Copy Markdown
Contributor

Assuming I'm reading the tags right, you mark this as a "defined term," but just drop the link to the definition. I don't feel like that helps, since you now have a dangling defined term.

@mnot
Copy link
Copy Markdown
Member Author

mnot commented Mar 25, 2020

@MikeBishop as I said in #311, this is the most minimal approach. To do more, I think we need to rename 4. Header and Trailer Fields to something like "Messages", and expand its introduction accordingly.

Any thoughts about that?

@MikeBishop
Copy link
Copy Markdown
Contributor

It seems like most of the content you'd want for defining a message is already there in 2.1:

Nevertheless, a common abstraction is that a message includes some form of envelope/framing, a potential set of named fields up front (a header section), a potential body, and a potential following set of named fields (a trailer section).

Rearranging text a little to put that definition (and make it a definition, rather than "a common abstraction") by the introduction of the term "message" seems like it would work without having to rearchitect Section 4.

@mnot
Copy link
Copy Markdown
Member Author

mnot commented Apr 27, 2020

@MikeBishop x:dfn denotes use of a defined term, not a primary definition.

@mnot
Copy link
Copy Markdown
Member Author

mnot commented Apr 27, 2020

@royfielding ?

@mnot mnot merged commit 8079d96 into master Apr 27, 2020
@mnot mnot deleted the mnot-311 branch April 27, 2020 23:03
triple-underscore added a commit to triple-underscore/triple-underscore.github.io that referenced this pull request Apr 29, 2020
httpwg/http-core#343
• Adjust multiple Content-Length handling

httpwg/http-core#346
• Rework invalidation definition
• Roy's suggestions
• grammar

httpwg/http-core#353
• Make text body narrower for readability

httpwg/http-core#354
• Remove H1-specific connection-related requirements
• Roy's feedback

httpwg/http-core#316
• map request target to target URI/resource
• fix one leftover of "effective request URI"
• Adjust anchor names
• push note into <aside> and move index entry
• sort change log
• restore indentation
• re-add missing closing brackets
• fix change log section title
• fix change log
• remove semantics HTML too
• removing HTML from PR

httpwg/http-core#344
• Don't rely on the HTTP/1.1 Messaging specification to define "message"

httpwg/http-core#357
• Present If-[none]-Match evaluation more clearly

httpwg/http-core#72
• Semantics of If-Match

httpwg/http-core#345
• remove ref to close option
• remove HTML from PR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Define "request" and "response" independent of HTTP/1.1

4 participants