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
Extend to allow standard websockets #2760
Comments
while this is unironically a good suggestion, it's gonna be difficult to implement a new peer type, which would still be undocumented, same as the current webrtc peer for webtorrent, which after all these years isn't documented lol, but +1 |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of this package are you using?
2.1.37
What problem do you want to solve?
Make it easier to push files to a headless server from the browser.
Simultaneously send files to workers (ie, peertube-runners) before upload is finished.
Resumable uploads.
What do you think is the correct solution to this problem?
Webrtc still seems too flaky to be relied upon in webtorrent-hybrid. Extend Webtorrent to have
WebsocketServer
andWebsocketClient
as new peer types. This way the server is guaranteed to be able to download from at least one peer in the swarm.Are you willing to submit a pull request to implement this change?
Yes, but I'd need advice on where to make changes. (Should it be
webtorrent/lib
orbittorrent-protocol
or somewhere else?)The text was updated successfully, but these errors were encountered: