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

Block-Wise Transfers (RFC 7959) #6

Open
3 of 8 tasks
NZSmartie opened this issue Dec 2, 2017 · 1 comment
Open
3 of 8 tasks

Block-Wise Transfers (RFC 7959) #6

NZSmartie opened this issue Dec 2, 2017 · 1 comment
Assignees

Comments

@NZSmartie
Copy link
Owner

NZSmartie commented Dec 2, 2017

This is an outline of my progress of implementing RFC 7959.

Note: Block1 is request payload to a resource. Block2 is a response from a resource.

CoapClient

  • Block1
    • Sending messages
    • Reduce block size on response
    • Restart Block-Wise transfer on block 0 when received a 4.14 - RequestEntityTooLarge
    • Fail Bloc-kWise transfer on when received a 4.14 - RequestEntityTooLarge
    • Reduce re-transmit attempts
  • Block2
    • Receiving messages
    • Cancel receiving

CoapServer

  • Block2
    • Respond with block-wise transfer.
  • More to add soon
@NZSmartie NZSmartie self-assigned this Dec 2, 2017
@NZSmartie
Copy link
Owner Author

Need to make sure the Stream interface behaviour is used properly.
At the moment. When invoking Write, the data is queued and returns immediately.
Instead. the write operation should begin right away (if possible). and write as many full blocks then return. the last incomplete block should be the only thing to write during a Close or Dispose

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant