Skip to content

Conversation

c2bo
Copy link
Member

@c2bo c2bo commented Sep 15, 2025

Closes #302

Wording feels somewhat rough, but I think this is the best place to add that note. Any ideas to improve wording?

@c2bo
Copy link
Member Author

c2bo commented Sep 15, 2025

cc @babisRoutis - couldn't request your review for some reason?

Copy link

@babisRoutis babisRoutis left a comment

Choose a reason for hiding this comment

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

Crystal clear 🔮

@paulbastian
Copy link
Contributor

We should also clarify, that the CWT/JWT goes into the HTTP response body?

@c2bo
Copy link
Member Author

c2bo commented Sep 17, 2025

We should also clarify, that the CWT/JWT goes into the HTTP response body?

That is why i added this sentence - I guess we could add the JWT one?

This means that the body of an HTTP response contains the raw CBOR bytes.

@paulbastian
Copy link
Contributor

We should also clarify, that the CWT/JWT goes into the HTTP response body?

That is why i added this sentence - I guess we could add the JWT one?

This means that the body of an HTTP response contains the raw CBOR bytes.

Yes, clarify further up for both JWT and CWT and have the reference to CWT encoding speed there as well. Let the now only talk about the hex encoding of examples underneath.

@c2bo
Copy link
Member Author

c2bo commented Sep 17, 2025

Moved the whole note up - seemed more logical if we already state something about the body of the http response here.

Copy link

@babisRoutis babisRoutis left a comment

Choose a reason for hiding this comment

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

Hi @c2bo

Now it looks even better.

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

Successfully merging this pull request may close these issues.

Clarification : Status List Token (in CWT) to the HTTP Response
3 participants