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

FETCH and blockwise - Behavior change of Californium 3.8 #2168

Closed
boaks opened this issue Aug 28, 2023 · 0 comments
Closed

FETCH and blockwise - Behavior change of Californium 3.8 #2168

boaks opened this issue Aug 28, 2023 · 0 comments

Comments

@boaks
Copy link
Contributor

boaks commented Aug 28, 2023

See the discussion in PR #2088 and Send request body when requesting Block2 messages for some more details.

The current implementation of a blockwise FETCH (bock2 only) sends the payload only in the first request. The follow up request do not contain the payload. With that, it's not possible to implement a stateless sever. Changing that, will require more data volume.

When Californium acts as server, Californium uses the client's identity (maybe the ip-address or the principal, depending on some configuration) and the URI including the URI-query to match a blockwise transfer. Since version 3.9, PR #2161 added also the message code to that. Californium's uses state for its implementation.

For a mixed block1/block2 transfer this seems to be unclear, what the best behavior will be.

If you're interested, please write us, what your preference will be.

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

No branches or pull requests

1 participant