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

messagepack #212

Open
jaytaph opened this issue Oct 11, 2022 · 0 comments
Open

messagepack #212

jaytaph opened this issue Oct 11, 2022 · 0 comments

Comments

@jaytaph
Copy link
Member

jaytaph commented Oct 11, 2022

Having a separate header.json, catalog.json and 0 or more blocks might not be the best way to manage messages. Instead, having a single file with the message would be "better".

In that case, we could have a packed-message format. Maybe we shouldn't bother too much with inventing something new, and just use plain tar for this.

During transmission, we still use all the parts separately, but once stored on a server, we could pack it.

We have to figure out if this actually would work with things like scanning files etc

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

No branches or pull requests

1 participant