This is a pretty good idea I think, though it would be good I think to make sure you still use the metadata in the Message trait to check the flows.
Look at https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/http-wrapper/src/server.rs#L183 and line 202: this enforces that the flow of messages doesn't get broken (i.e. a later message sent without the prior setup) and that messages that need to be encrypted are that way, etc.
I'd strongly suggest to keep using this same data, since making someone add this to each route will fail eventually (someone will forget to add the check at some point).

This is a pretty good idea I think, though it would be good I think to make sure you still use the metadata in the Message trait to check the flows.
Look at https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/http-wrapper/src/server.rs#L183 and line 202: this enforces that the flow of messages doesn't get broken (i.e. a later message sent without the prior setup) and that messages that need to be encrypted are that way, etc.
I'd strongly suggest to keep using this same data, since making someone add this to each route will fail eventually (someone will forget to add the check at some point).

awesome thanks for the input @puiterwijk !! cc @7flying

This is a pretty good idea I think, though it would be good I think to make sure you still use the metadata in the Message trait to check the flows. Look at https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/http-wrapper/src/server.rs#L183 and line 202: this enforces that the flow of messages doesn't get broken (i.e. a later message sent without the prior setup) and that messages that need to be encrypted are that way, etc. I'd strongly suggest to keep using this same data, since making someone add this to each route will fail eventually (someone will forget to add the check at some point).

Thanks for pointing that out 🙏

The idea is not to change the traits/structs nor the logic, just the types so that everything stays the same but with a different framework underneath.