FIX/Fix the BroadCast File Transfer #11
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
|
My take on this is I have an Acknowledgment system(NACK) that checks whether all the packets have arrived or not. If not, the system says that these packets [Sequence Number] are not present and again retransmits those missing packets. |
|
could you share a video of this working also can you test this against the tcp based approach to see if your approach actually to quantize the effect of changing to your approach |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
added a header to each packet with a session ID and sequence number. After the initial broadcast, receivers send NACKs (Negative Acknowledgements) listing any missing packets. The sender then re-broadcasts only those missing chunks, ensuring a complete and ordered file.
To improve flexibility, hardcoded network addresses were moved to a configuration file. The receiver now safely buffers chunks before writing to disk, preventing file corruption from out-of-order packets. This makes the broadcast fast, resilient to packet loss, and stable.
Related Issue
Fixes #3 (issue)
Type of change
Motivation and Context
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Screenshots (if appropriate):
Checklist:
Test Configuration: