From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] mDNS
Date: Sat, 2 Jan 2016 09:41:48 -0800 [thread overview]
Message-ID: <c0c888aa9a7911b078c8b1dbee12c4a1@mule> (raw)
In-Reply-To: <CA293B6C-0B46-4F5E-85F5-E081CE87ED93@quintile.net>
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
prev parent reply other threads:[~2016-01-02 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 9:29 Steve Simon
2016-01-02 17:41 ` erik quanstrom [this message]
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=c0c888aa9a7911b078c8b1dbee12c4a1@mule \
--to=quanstro@quanstro.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).