| « Last codeplex project address change | Posts en français » |
Bonjour and DNS .NET implementation
Hello,
I've recently published on codeplex a partial object DNS protocol implementation and an implementation of Apple's Bonjour protocol. You may ask me why implement this DNS protocol whilst a .NET Dns class exists. First of all, because the Dns class is based on Win32 API, which, I don't want. Secondly, because my DNS implementation is mDNS (multicast DNS) compliant, and Bonjour relies on this protocol. At last, and not the least, for fun !
Let's stop talking and discover it...
2 comments
Comment from: Thomas Salvisberg [Visitor]
Thank you a thousand times!
I've been looking for this for some time and knew that I don't have the brains to implement it myself.. ;)
I've been looking for this for some time and knew that I don't have the brains to implement it myself.. ;)
01/23/09 @ 19:01
Comment from: brian dunnington [Visitor] · http://www.growlforwindows.com
first, let me thank you for the great project - it is just what i was looking for.
after struggling with bugs trying to P/Invoke the dnssd.dll (Apple's Bonjour), i decided i needed to change course. your library is just the ticket and was easy to implement.
the only question i have so far is how to actively unpublish a server. i set up my Service and call .Publish() when my app starts, and when the app shuts down, i call .Stop(). but in another apps that uses your library as a BonjourServiceBrowser, the ServiceRemoved event is never fired, so the browsing app still things the service is availalbe after it shuts down. got any advice?
after struggling with bugs trying to P/Invoke the dnssd.dll (Apple's Bonjour), i decided i needed to change course. your library is just the ticket and was easy to implement.
the only question i have so far is how to actively unpublish a server. i set up my Service and call .Publish() when my app starts, and when the app shuts down, i call .Stop(). but in another apps that uses your library as a BonjourServiceBrowser, the ServiceRemoved event is never fired, so the browsing app still things the service is availalbe after it shuts down. got any advice?
08/21/09 @ 18:37
Comment feed for this postComments are closed for this post.