From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New USE_EXPAND flag for www-servers/monkeyd
Date: Tue, 28 May 2013 15:22:04 -0400 [thread overview]
Message-ID: <51A503DC.4080200@gentoo.org> (raw)
In-Reply-To: <20130528210737.42695fc9@gentoo.org>
On 05/28/2013 03:07 PM, Michał Górny wrote:
> On Tue, 28 May 2013 14:57:03 -0400
> "Anthony G. Basile" <blueness@gentoo.org> wrote:
>
>> On 05/28/2013 11:35 AM, Michał Górny wrote:
>>> On Mon, 27 May 2013 16:38:09 -0400
>>> "Anthony G. Basile" <blueness@gentoo.org> wrote:
>>>
>>>> I was about to add a use expand flag for monkeyd (a tiny web server) and
>>>> there is a notice in base/make.default to discuss use expand flags on
>>>> the list first. There are about 9 plugins for monkeyd similar to apache
>>>> which can be turned on/off by a configure switch. It makes sense to
>>>> follow the same logic as apache here. There are no dependencies on
>>>> monkeyd and so no use-deps. Seems very safe. Any objections?
>>> Could you elaborate a bit more on the flags? Please list them, shortly
>>> explain and tell us whether you expect the number of plugins to expand
>>> and how fast.
>>>
>> Sorry I already committed this with Chainsaw's ack. Anyhow, they are:
>>
>> auth - Provide HTTP Basic Authentication
>> cheetah - Provide a shell-like command line interface
>> #cgi - Provide the traditional CGI interface
>> dirlisting - Show an HTML listing of the content of a directory
>> #fastcgi - Provide FastCGI proxy support
>> liana - Build your own network layer through monkeyd
>> logger - Log requests and common errors
>> mandril - Restrict incoming connections based on the IP address or URI
>> request
>> polarssl - Provide HTTPS using PolarSSL v1.*.
> Shouldn't this one be tied to USE=ssl?
>
> For the others, how large is the benefit of having them switchable?
> At least some of them look like something that wouldn't hurt people if
> it was always-built.
>
I thought about ssl but I'm still not sure if USE=ssl means just openssl
or any ssl. Eg, with curl, which has a choice of one of six backend ssl
providers, I changed USE=ssl to mean that one and only one of the six
must be on. Previously though, USE=ssl in curl meant only openssl which
was confusing because you could also have USE=nss or gnutls etc provide
your ssl. monkey also bounced around its ssl backend from liana_ssl to
polarssl which is what made me think of curl. What if in the future
there's yet another ssl backend? Although use.desc does say ... "ssl -
Adds support for Secure Socket Layer connections". Any advice here?
monkeyd is intended for embedded systems which is why it has switchable
plugins. You can even choose whether or not to install the shared lib
and include files to really slim it down.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2013-05-28 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 20:38 [gentoo-dev] New USE_EXPAND flag for www-servers/monkeyd Anthony G. Basile
2013-05-28 6:01 ` Tony "Chainsaw" Vroon
2013-05-28 11:30 ` Anthony G. Basile
2013-05-28 6:24 ` René Neumann
2013-05-28 15:35 ` Michał Górny
2013-05-28 18:57 ` Anthony G. Basile
2013-05-28 19:07 ` Michał Górny
2013-05-28 19:22 ` Anthony G. Basile [this message]
2013-05-28 20:18 ` Michał Górny
2013-05-31 13:23 ` Gilles Dartiguelongue
2013-05-28 22:15 ` William Hubbs
2013-05-30 11:23 ` Ralph Sennhauser
2013-06-01 17:41 ` William Hubbs
2013-06-01 18:00 ` Michał Górny
2013-06-01 20:20 ` William Hubbs
2013-06-01 20:26 ` Michał Górny
2013-06-02 0:21 ` William Hubbs
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=51A503DC.4080200@gentoo.org \
--to=blueness@gentoo.org \
--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