-
Notifications
You must be signed in to change notification settings - Fork 18
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
Public DNS-SD API for browsing, resolving, and publishing services #19
Comments
The proposed API manages all DNS-SD requests/registrations on a separate thread represented by the Create/destroy DNS-SD context:
Create/destroy browsing request:
Create/destroy query request:
Create/restore resolve request:
Create/destroy named services. Each service has a name and one or more instances:
|
Mostly done, just have the Windows DNS-SD APIs to support. |
Created #29 to track usage of the Windows DNS-SD APIs. Closing this one. |
Currently the various bits of CUPS, PAPPL, etc. have a conditional mess of code that use the Avahi or mDNSResponder APIs to do DNS-SD discovery and sharing. This continues to be a major pain, and CUPS should have a common API that developers can use to access whatever the local API/service is for this. Goals:
The text was updated successfully, but these errors were encountered: