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

Explain how range requests work with SDK #279

Open
tzarebczan opened this issue May 20, 2019 · 0 comments
Open

Explain how range requests work with SDK #279

tzarebczan opened this issue May 20, 2019 · 0 comments

Comments

@tzarebczan
Copy link
Contributor

This should be a new guide on how to use range requests with the SDK.
Summary:
Seekable downloads and range request support
This release adds seekable streaming downloads and playback via HTTP range requests at http://<streaming_server>/stream/<sd_hash>, as well as new configuration settings streaming_server (default: localhost:5280) and streaming_get (default: True). For convenience, File type api response objects have a new streaming_url string at which the partial content stream can be requested. Only files already in the file manager can be streamed via range requests, if given an sd hash of an unknown stream the server will respond with a 404 error.
Provided thestreaming_get setting is not disabled, new streams can be requested from a claim name and optional claim id at http://<streaming_server>/get/ or http://<streaming_server>/get//<claim_id>. These will internally call the api method get and return an http redirect to the /stream endpoint.
Writing downloads to the file system can now be disabled or enabled by default using the new save_files setting. The existing get command will follow this setting but can be overridden with the new save_file argument.
The added file_save command will explicitly save a file to disk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant