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

[k2] top-level wire protocol spec and encoding implementation #26

Closed
neonphog opened this issue Nov 27, 2024 · 0 comments · Fixed by #38
Closed

[k2] top-level wire protocol spec and encoding implementation #26

neonphog opened this issue Nov 27, 2024 · 0 comments · Fixed by #38
Assignees

Comments

@neonphog
Copy link
Collaborator

This spec should include:

  • the encoding format (messagepack)
  • the exact encoding parameters (structs are maps, names are camelCase or whatever we agree on)
  • a method for rejecting connections on implementer defined whim (i.e. holochain switch to dht v2, so it's no longer compatible)
  • preflight validation (prove we have at least one space in common that we are both allowed to speak on)
  • send/recv arbitrary opaque specific module implementation data. I.e. not just "the dht module" we need to know to send it to the actual "dht_v1" module.
@github-project-automation github-project-automation bot moved this to Backlog in Holochain Nov 27, 2024
@holochain holochain deleted a comment Nov 27, 2024
@neonphog neonphog self-assigned this Dec 2, 2024
@neonphog neonphog moved this from Backlog to In progress in Holochain Dec 2, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in Holochain Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant