-
-
Notifications
You must be signed in to change notification settings - Fork 745
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
JSON API: Missing bits and pieces #2274
Comments
Excuse me if it's a dumb question, but why not msgpack? |
@Abogical json is easier for this and we do not have the high efficiency / throughput requirements here. |
Because possibly-binary contents are so far an exception I chose JSON for this first implementation (e.g. not-entirely-complete paths in a progress update are not important - plus, a binary path can't be really rendered as text anyway –– but they might be annoying for "borg list --json", for example). [1] https://borgbackup.readthedocs.io/en/latest/internals/frontends.html |
Guess concerning msgpack vs json, the decision was made long ago. About binary items: we have a more specific ticket about this. #6151 Considering all else, this ticket is too unspecific. |
From #2249
The text was updated successfully, but these errors were encountered: