From: Steve Simon <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] mDNS
Date: Sat, 2 Jan 2016 09:29:43 +0000 [thread overview]
Message-ID: <CA293B6C-0B46-4F5E-85F5-E081CE87ED93@quintile.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
mmmm,
I am confused, are you talking of replacing the interface to dns(1)?
I had no real plan, maybe to just make mDNS accumulate broadcast and
multicast mDNS messages into a virtual file in /lib/ndb format.
more importantly I really need a publish system, which would be just based off
/lib/ndb/local, just a static spec.
my target is porting shairport, and maybe Dnla at a later date.
-Steve
> On 2 Jan 2016, at 03:42, erik quanstrom <quanstro@quanstro.net> wrote:
>
>> On Fri Jan 1 19:32:25 PST 2016, marc@boschma.cx wrote:
>>
>>> On 2 Jan 2016, at 7:05 am, Steve Simon <steve@quintile.net> wrote:
>>> anyone done any work to implement mDNS / bonjour on plan9?
>>
>> No, but I have an interest; just starting out with Plan9 :)
>>
>>> my rough plan is to write a file server which generates /lib/ndb/mdns
>>> which can be included into your /lib/ndb/local.
>>>
>>> I fear the biggest hassle is the clash of UDP port use may mean
>>> mDNS must become part of dns(1) rather than a separate file server.
>>
>> Shouldn’t dns(1) only bind to unicast UDP port and thus mDNS could bind to the multicast UDP port?
>>
>> Are you only considering resolution or also publishing services?
>
> it would make sense to me to make a dnsudp request file server that manages requests, and
> fork (ha!) that task off to it. this file server would not care if it's querying normal dns,
> or mdns.
>
> - erik
[-- Attachment #2: Type: text/html, Size: 5475 bytes --]
next reply other threads:[~2016-01-02 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 9:29 Steve Simon [this message]
2016-01-02 17:41 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA293B6C-0B46-4F5E-85F5-E081CE87ED93@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).