Fix fragmentation bug #147
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix fragmentation bug in final frame
Motivation:
If the final frame of a stream is fragmented - only the last fragment should have the (C)omplete flag set.
Currently - the first fragment has the (C)omplete flag set - which is a bug - because a receiver may assume that the stream is complete even though more fragments are coming.
(F) and (C) flags are essentially mutually exclusive.
Modifications:
Ensure (C)omplete flag is unset for all fragments besides the last one (i.e. fragments with (F)ollow flag set).
Result:
The logic now handles the (C)omplete flag correctly for fragmented frames.