Skip to content

Add client_id and name to the _resonate mDNS service type #20

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.

Sign up for GitHub

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add client_id and name to the _resonate mDNS service type #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,10 @@ Resonate Servers must support both methods described below.
Clients announce their presence via mDNS using:
- Service type: `_resonate._tcp.local.`
- Port: The port the Resonate client is listening on (recommended: `8927`)
- TXT record: `path` key specifying the WebSocket endpoint (recommended: `/resonate`)
- TXT records:
- `path` key specifying the WebSocket endpoint (recommended: `/resonate`)
- `client_id` key specifying the unique client identifier, same as used in the `client/hello` message
- `name` key specifying a friendly name for the client, same as used in the `client/hello` message

The server discovers available clients through mDNS and connects to each client via WebSocket using the advertised address and path.

Expand Down