From: Matt Benjamin <mbenjamin@redhat.com>
To: Radoslaw Zarzynski <rzarzynski@mirantis.com>
Cc: Casey Bodley <cbodley@redhat.com>,
The Sacred Order of the Squid Cybernetic
<ceph-devel@vger.kernel.org>
Subject: Re: rgw: feedback on auth engine selection
Date: Thu, 8 Sep 2016 17:05:42 -0400 (EDT) [thread overview]
Message-ID: <1857033161.83221781.1473368742739.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+H5UW2nL1nWa6YFW7yoiuu0WE-rYxYjMpm1X+Tw6_LbvSrwwQ@mail.gmail.com>
Hi,
inline
----- Original Message -----
> From: "Radoslaw Zarzynski" <rzarzynski@mirantis.com>
> To: "Casey Bodley" <cbodley@redhat.com>
> Cc: "The Sacred Order of the Squid Cybernetic" <ceph-devel@vger.kernel.org>
> Sent: Thursday, September 8, 2016 1:19:11 PM
> Subject: Re: rgw: feedback on auth engine selection
>
>
> At the moment RGWHandler is dynamically allocated on each
> request. Do we plan to remove only the allocations or go even
> further and make handlers entirely state-less?
That's been on my list of things to eventually do, for a while--in the librgw front-end, it already is.
>
> > - req_state: contains too many unrelated fields, some of which are
> > transformed in confusing ways over the lifetime of the request. needs to be
> > broken up into smaller, better encapsulated sub-objects
>
> I'm 100% behind that.
Me too. Eventually, I'd like avoid needing separate allocations for any subobjects. This was one of the main places I hoped we copuld use the polymorphic union idea that you called "static pointer." :)
>
> > - concurrency: move away from a synchronous process_request() to build on
> > asio frontend work
>
> Sound really interesting.
>
>
> Let me propose another requirement:
> - critical components should facilitate unit testing. In the future
> they should be covered by reasonable set of unit tests.
sure
>
> What do you think?
>
> Regards,
> Radek
> --
> 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
>
--
Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://www.redhat.com/en/technologies/storage
tel. 734-707-0660
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2016-09-08 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e2a2e0c9-51e7-b703-2c8d-7b489d4e8994@redhat.com>
2016-09-07 17:19 ` rgw: feedback on auth engine selection Radoslaw Zarzynski
2016-09-07 21:05 ` Casey Bodley
2016-09-08 17:19 ` Radoslaw Zarzynski
2016-09-08 18:23 ` Casey Bodley
2016-09-12 9:48 ` Radoslaw Zarzynski
2016-09-12 18:35 ` Casey Bodley
2016-09-08 21:05 ` Matt Benjamin [this message]
2016-09-08 17:21 ` Pritha Srivastava
2016-09-09 15:43 ` Radoslaw Zarzynski
2016-09-07 21:09 ` Casey Bodley
2016-09-08 15:46 ` Radoslaw Zarzynski
2016-09-08 20:49 ` Casey Bodley
2016-09-11 23:20 ` Radoslaw Zarzynski
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=1857033161.83221781.1473368742739.JavaMail.zimbra@redhat.com \
--to=mbenjamin@redhat.com \
--cc=cbodley@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=rzarzynski@mirantis.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.