You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: