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

feat: nestri-server resiliency, ICE trickling and WebSocket as initiator connection #137

Merged
merged 14 commits into from
Nov 28, 2024

Conversation

DatCaptainHorse
Copy link
Collaborator

Using the same WebRTC connection as DataChannel inputs, though switched it to WHIP etc.

Draft since I'm still looking into some stuff.

@DatCaptainHorse DatCaptainHorse changed the title feat: nestri-server resiliency feat: nestri-server resiliency, ICE trickling and WebSocket as initiator connection Nov 26, 2024
@DatCaptainHorse DatCaptainHorse marked this pull request as ready for review November 26, 2024 11:41
@DatCaptainHorse
Copy link
Collaborator Author

nestri-server is now resilient to relay deaths, connection losses etc.
also added ICE trickling for hyper-speed WebRTC connections

other improvements as well 😅

@DatCaptainHorse
Copy link
Collaborator Author

Whew.. that's a lotta changes, but we got WebSockets now :P

Copy link
Member

@wanjohiryan wanjohiryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :P

@wanjohiryan wanjohiryan merged commit 9a26db8 into nestrilabs:feat/stream Nov 28, 2024
DatCaptainHorse added a commit to DatCaptainHorse/nestri that referenced this pull request Dec 8, 2024
…tor connection (nestrilabs#137)

Using the same WebRTC connection as DataChannel inputs, though switched
it to WHIP etc.

Draft since I'm still looking into some stuff.

---------

Co-authored-by: DatCaptainHorse <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants