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

MOQT: Implement stream buffer to support parsing uintvar message headers #164

Closed
TimEvens opened this issue May 28, 2024 · 0 comments · Fixed by #165
Closed

MOQT: Implement stream buffer to support parsing uintvar message headers #164

TimEvens opened this issue May 28, 2024 · 0 comments · Fixed by #165
Assignees

Comments

@TimEvens
Copy link
Contributor

MOQT does not have a message header length field, only a series of uintvar params. This requires libquicr to parse received messages uintvar by uintvar to get the size of the header and data, even with control messages.

Implement stream buffer APi changes and refactor existing messages to support stream buffer parsing instead of received objects (HDR + data).

@TimEvens TimEvens self-assigned this May 28, 2024
@TimEvens TimEvens added the enhancement New feature or request label May 28, 2024
TimEvens added a commit that referenced this issue May 28, 2024
* Resolves #164
* Add fixed 4 byte length to all wire messages
* Remove RX metrics that are no longer supported
* Add datagram metrics to connection export
* Add method to client/server sessions for control messages
* Implement transport stream buffer API changes
@TimEvens TimEvens added moq-phase1 and removed enhancement New feature or request labels May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant