From: Nathan Cutler <ncutler@suse.cz>
To: Ken Dreyer <kdreyer@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: apache/fcgi deprecation?
Date: Tue, 9 Feb 2016 00:07:20 +0100 [thread overview]
Message-ID: <56B91FA8.8080709@suse.cz> (raw)
In-Reply-To: <CALqRxCxtJ5a0xB68kSNP7xr3qcJ-rEr=xP+ByqyusyuOWU2HgQ@mail.gmail.com>
On 02/08/2016 11:57 PM, Ken Dreyer wrote:
> Sure, please do it!
>
> I think it's just a matter of no one having time to remove it.
So we could remove the FastCGI dependency from the packaging, too?
> On Thu, Feb 4, 2016 at 9:12 PM, Nathan Cutler <ncutler@suse.cz> wrote:
>> I was just browsing the RGW documentation and noticed that parts of it are
>> still apache/fcgi-oriented (with no mention of civetweb) even in master.
>>
>> My impression was that civetweb is now recommended for RGW deployments as it
>> is faster. Is that true? And is there a plan to deprecate/drop apache/fcgi
>> support, or will it remain indefinitely?
>>
>> Would it be a good idea to expunge apache/fcgi from the docs and point folks
>> to civetweb instead?
>>
>> --
>> Nathan Cutler
>> Software Engineer Distributed Storage
>> SUSE LINUX, s.r.o.
>> Tel.: +420 284 084 037
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
next prev parent reply other threads:[~2016-02-08 23:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 4:12 apache/fcgi deprecation? Nathan Cutler
2016-02-08 22:57 ` Ken Dreyer
2016-02-08 23:07 ` Nathan Cutler [this message]
2016-02-09 0:30 ` Sage Weil
2016-02-09 1:16 ` Yehuda Sadeh-Weinraub
2016-02-09 1:56 ` Matt Benjamin
2016-02-09 2:40 ` Blair Bethwaite
2016-02-09 4:09 ` Ken Dreyer
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=56B91FA8.8080709@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.