From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Simon Content-Type: multipart/alternative; boundary=Apple-Mail-86029C4E-3A4C-4353-A0E3-DF800F28F406 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Message-Id: Date: Sat, 2 Jan 2016 09:29:43 +0000 To: 9fans@9fans.net Subject: [9fans] mDNS Topicbox-Message-UUID: 7d1e6a9a-ead9-11e9-9d60-3106f5b1d025 --Apple-Mail-86029C4E-3A4C-4353-A0E3-DF800F28F406 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable mmmm,=20 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 o= ff /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 wrote: >=20 >> On Fri Jan 1 19:32:25 PST 2016, marc@boschma.cx wrote: >>=20 >>> On 2 Jan 2016, at 7:05 am, Steve Simon wrote: >>> anyone done any work to implement mDNS / bonjour on plan9? >>=20 >> No, but I have an interest; just starting out with Plan9 :) >>=20 >>> my rough plan is to write a file server which generates /lib/ndb/mdns >>> which can be included into your /lib/ndb/local. >>>=20 >>> 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. >>=20 >> Shouldn=E2=80=99t dns(1) only bind to unicast UDP port and thus mDNS coul= d bind to the multicast UDP port? >>=20 >> Are you only considering resolution or also publishing services? >=20 > it would make sense to me to make a dnsudp request file server that manage= s requests, and > fork (ha!) that task off to it. this file server would not care if it's q= uerying normal dns, > or mdns. >=20 > - erik --Apple-Mail-86029C4E-3A4C-4353-A0E3-DF800F28F406 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

mmmm, 
<= div>
I am confu= sed, are you talking of replacing the interface to dns(1)?
=
<= div>I had no real p= lan, 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 sp= ec.

my target is porting shairport, and maybe Dnla at a later date.

-S= teve


On 2 Jan 2016, at 03:42, erik quanstrom <quanstro@quanstro.net> wrote:

<= /span>
On Fri Jan  1 19:32:= 25 PST 2016, marc@boschma.cx wrote:

On 2 Jan 2016, a= t 7:05 am, Steve Simon <steve@quint= ile.net> wrote:
anyone done any work to impl= ement mDNS / bonjour on plan9?

No, but I have an interest; just starting out with Plan9 :)
=

my r= ough 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=E2=80=99t dns(1) only bind to unicast UDP po= rt and thus mDNS could bind to the multicast UDP port?

Are you only considering resolution or also publ= ishing services?

it would make sense to m= e to make a dnsudp request file server that manages requests, and
fork (h= a!) that task off to it.  this file server would not care if it's query= ing normal dns,
or mdns.

- erik= --Apple-Mail-86029C4E-3A4C-4353-A0E3-DF800F28F406-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 2 Jan 2016 09:41:48 -0800 To: 9fans@9fans.net Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] mDNS Topicbox-Message-UUID: 7d330e0a-ead9-11e9-9d60-3106f5b1d025 On Sat Jan 2 01:31:36 PST 2016, steve@quintile.net wrote: > > 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. that wasn't what i had in mind at all. dns(1) does a whole bunch of things, including. - answering queries via /net/dns - answering queries via udp, and tcp, - maintence of database ndb files - resursive resolution via udp or tcp - caching of results currently these functions are all in ndb/dns, and there isn't even threading. that seems like a hard structure to maintain. - erik