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.

Sign up for GitHub

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

Jump to bottom

Blockwise transfers not queued if conflicting #58

Open
chrysn opened this issue Mar 8, 2017 · 1 comment
Open

Blockwise transfers not queued if conflicting #58

chrysn opened this issue Mar 8, 2017 · 1 comment
Labels
blockwise

Comments

@chrysn
Copy link
Owner

chrysn commented Mar 8, 2017

Simultaneous blockwise (block1) requests to the same resource can not be distinguished in CoAP and thus need to be serialized or originate from different ports.

Neither happens, causing test_blockwise..test_sequential to fail.

Planned fix is the block handler noting in-progress transfers and queueing up (or maybe failing in case of NONs) the second request.
chrysn added a commit that referenced this issue Mar 8, 2017
@chrysn
Test behavior of concurrent POSTs to a single resource
8fc2d69 
The test fails (as expected), which opens a different issue
(#58) but
closes: #56
@chrysn
Copy link
Owner Author

chrysn commented Oct 20, 2021

As an alternative to serializing, they could also use Request-Tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blockwise
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chrysn