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

Explain use of framers for connectionless protocols #1023

Merged
merged 4 commits into from Jun 15, 2022
Merged

Conversation

tfpauly
Copy link
Contributor

@tfpauly tfpauly commented May 17, 2022

Closes #538

@chrysn
Copy link

chrysn commented May 20, 2022

That change would have helped me understand what framers can do. It seems a bit out of sync with " A Framer can encapsulate or encode outbound Messages, and decapsulate or decode inbound data into Messages." which sounds like it'd preclude operations like processing received data (or whole messages) into connection object state without emitting a message again -- maybe that sentence could be extended along with it (if even just to include "for example" or "or modify the connection object").

@tfpauly
Copy link
Contributor Author

tfpauly commented Jun 15, 2022

@chrysn we've added some clarifying text in the message framer definition

draft-ietf-taps-impl.md Outdated Show resolved Hide resolved
@tfpauly tfpauly merged commit bd0bba9 into master Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Interface for app-driven racing of "unconnected" protocols?
4 participants