From: Michael Mol <mikemol@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Global useflags zeroconf and avahi
Date: Mon, 01 Apr 2013 23:08:11 -0400 [thread overview]
Message-ID: <515A4B9B.2060106@gmail.com> (raw)
In-Reply-To: <515A46D1.1010205@yahoo.ca>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On 04/01/2013 10:47 PM, Alex Xu wrote:
> Kill zeroconf and use "dnssd", "upnp", "ssdp". Problem solved?
I very much like the approach in principle, though. Digging briefly into
Wikipedia[1], UPnP has several components:
* AutoIP (IPv4LL)
* SSDP (So, a separate "ssdp" USE flag may not be necessary)
* SOAP (If I read this correctly, this is the encoding of its RPC
mechanism)
* GENA (A pub/sup architecture)
(For those that read the link, I'm obviously leaving out the
'Description' section...I don't know what that would be called, really.)
I don't know enough about real-world use of UPnP to say which of these
components are most fruitfully separated out of UPnP, USE-wise. If I had
to guess, I'd probably suggest:
* Break out SSDP and AutoIP,
* Have UPnP imply SOAP and GENA
* Have UPnP depend on the enabling of SSDP and AutoIP.
Or tie all of it into a single USE flag and be left with 'upnp' and 'ssdp'.
[1]
https://en.wikipedia.org/w/index.php?title=Universal_Plug_and_Play&oldid=543684744#Protocol
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
next prev parent reply other threads:[~2013-04-02 3:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 21:58 [gentoo-dev] Global useflags zeroconf and avahi Andreas K. Huettel
2013-04-01 22:16 ` Gilles Dartiguelongue
2013-04-01 22:42 ` Andreas K. Huettel
2013-04-02 19:46 ` Pacho Ramos
2013-04-02 20:34 ` Andreas K. Huettel
2013-04-01 22:27 ` Chí-Thanh Christopher Nguyễn
2013-04-01 22:43 ` Andreas K. Huettel
2013-04-02 2:47 ` Alex Xu
2013-04-02 3:08 ` Michael Mol [this message]
2013-04-02 5:06 ` Arun Raghavan
2013-04-02 7:43 ` Michał Górny
2013-04-02 23:06 ` Gilles Dartiguelongue
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=515A4B9B.2060106@gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/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