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

ReqResp encoded bytes API #5378

Closed
dapplion opened this issue Apr 18, 2023 · 1 comment · Fixed by #5417
Closed

ReqResp encoded bytes API #5378

dapplion opened this issue Apr 18, 2023 · 1 comment · Fixed by #5417
Assignees

Comments

@dapplion
Copy link
Contributor

Since ReqResp requests and responses must cross the worker boundary it's best to just wait to de-serialize them on the main thread. For it the API exposed by the reqresp package must deal exclusively with Uint8Array instead of T representing the deserialized object. For reference of how the API should look like PR #5229 is quasi complete reference.

@nazarhussain
Copy link
Contributor

Based on discussion with @wemeetagain came up with this diagram to align the understanding for everyone.

image

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 a pull request may close this issue.

2 participants