understanding intended use cases
Open
- Dominant language
- JavaScript
- Stars
- 209
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Hi, this is a really great lib.
Trying to understand the intended use cases, outside of webtorrent. From the top of my mind:
- open and read a file locally
- send and stream a local file to another browser using webrtc
- open a file downloaded from a remote server
- render live some file while being worked in the browser (like md->pdf)
Most of the use cases are relying on ReadableStream from browser API, I think. Is some kind of bridge between nodejs ReadableStream envisioned? That would need more fined grained API (to handle precache for instance).
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.