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

CoAP storage demo #350

Draft
wants to merge 14 commits into
base: main
Choose a base branch
from
Draft

CoAP storage demo #350

wants to merge 14 commits into from

Conversation

chrysn
Copy link
Collaborator

@chrysn chrysn commented Jul 4, 2024

Description

This is a first experiment with CoAP server access to the storage.

The README has an added section on how to GET and PUT values through encrypted CoAP

Issues/PRs references

Depends on #277 (CC'ing @kaspar030)
Depends on #348

Open Questions

  • When will I update the CoAP server handlers to be properly async so I don't need to rely on our backend not really being async? (If it were, things would just 5.00 Internal Server Error)
  • Will we need some storage multiplexing or run-time acquisition of the storage as soon as there are multiple handlers, either of which may access storage (or even if there is just one or it multiplexes internally, something non-CoAP and CoAP accesing it)?
  • Do we want/need to enumerate and type-introspect items? (Introspection would be limited to types known ahead of time, unless introspection gives us dyn and they are type safe so probably not, plus then it'd be really dangerous to persist this across firmware updates)
  • Is loading them from postcard internally, serde unpacking them and then serde serializing them for transport as CBOR a sensible thing to do? (Probably: This is a demo, after all)

Change checklist

  • Anything was done properly at all

    No: This is a very coarse thing right now, and is probably best rewritten from scratch after its dependencies have matured

kaspar030 and others added 13 commits April 30, 2024 09:21
@kaspar030
riot-rs-storage: initial commit
cb11398
@kaspar030
examples/storage: playground
cf1e0f4
@kaspar030
fixup! riot-rs-storage: initial commit
0e4c5a1
@chrysn
refactor(coap): Move server/client mechanism from example into coapcore
598c537
@chrysn
fix(coap): Minor lint fixes
6502105
@chrysn
build: Add riot-rs{-,::}coap
30f1716
@chrysn
refactor: Move CoAP stack setup into riot-rs-coap module
09a3cb0 
The security setup is not moved in yet.

Choices of address families are propagated into smoltcp to avoid
mismatches.
@chrysn
refactor(coap): Move crypto setup into riot-rs-coap
bf57daf
@chrysn
ci(doc): Enable CoAP module
83d39d9
@chrysn
fix(coap): Split and simplify example client code to avoid unwraps an…
ed56c41 
…d enhance error handling
@chrysn
fix(coap): Restore building with IPv6 enabled
000d917
@chrysn
Merge remote-tracking branch 'kaspar/riot-rs-storage' into coap-storage
df45ed8
@chrysn
experimental: CoAP storage server
34333d9
ROMemories
ROMemories reviewed Jul 5, 2024
View reviewed changes
examples/coap/README.md
@@ -19,6 +19,17 @@ This application is a work in progress demo of running CoAP with OSCORE/EDHOC se
up to the maximum number of security contexts that are stored (currently 4).
* There is also `./fauxhoc.py`, which did EDHOC manually before it was integrated in aiocoap.

### Storage

```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
```
```sh

?

@chrysn chrysn mentioned this pull request Jul 5, 2024
Draft
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ROMemories ROMemories ROMemories left review comments

Assignees
No one assigned
Labels
network
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@chrysn @ROMemories @emmanuelsearch @kaspar030