You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2020. It is now read-only.
It is not clear from just reading RFC001, how headers and body should be used.
Reason is: Message should be able to be parsed in a single pass, that requires headers to be able to be parsed orthogonally (i.e. they don't depend on each other).
Contrary, field names and datatypes in body may depend on the value of headers.
The text was updated successfully, but these errors were encountered:
While reading RFC004 I again got the impression, that it's rather arbitrary, which information goes into headers and what goes into the body. IMHO this rather confuses instead of helps.
I would not let implementation details (such as single pass parsing) come into my way, when specifying the protocol
It is not clear from just reading RFC001, how headers and body should be used.
Reason is: Message should be able to be parsed in a single pass, that requires headers to be able to be parsed orthogonally (i.e. they don't depend on each other).
Contrary, field names and datatypes in body may depend on the value of headers.
The text was updated successfully, but these errors were encountered: