From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH backup] client: use build_authority in build_uri
Date: Thu, 6 May 2021 09:43:31 +0200 [thread overview]
Message-ID: <20210506074331.by6cuf7pmr6nrq4f@wobu-vie.proxmox.com> (raw)
In-Reply-To: <1181206651.274.1620286443593@webmail.proxmox.com>
On Thu, May 06, 2021 at 09:34:03AM +0200, Dietmar Maurer wrote:
> > On 05/06/2021 9:14 AM Wolfgang Bumiller <w.bumiller@proxmox.com> wrote:
> >
> >
> > On Thu, May 06, 2021 at 09:01:46AM +0200, Dietmar Maurer wrote:
> > > In general a good idea, but we now merge code
> > > from two independent http client implementation (making them
> > > dependent)?
> >
> > I mean... it's called "tools::http"... as in "http utilities", which
> > IMO does not really sound like "this is an independent http client,
> > which must not be reused"... ;-)
>
> What naming do you suggest instead?
I suppose I'd put shared http stuff in `tools::http` and if the client
should be separate I'd suggest `tools::http::client`, but I'm not
convinced it cannot stay as is while sharing some code in the first
place
>
> > And it's a rather thin layer around hyper (the *actual* client...) to
> > add proxy support which, too, is something that we may at some point
> > want to reuse without the rest of `SimpleHttp`, no?
>
> I am not sure if it is worth to reuse that for that backup client. We simply
> do not need proxy support there.
yet ;-)
next prev parent reply other threads:[~2021-05-06 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 7:34 Dietmar Maurer
2021-05-06 7:43 ` Wolfgang Bumiller [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-06 7:01 Dietmar Maurer
2021-05-06 7:14 ` Wolfgang Bumiller
2021-05-06 6:55 Wolfgang Bumiller
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=20210506074331.by6cuf7pmr6nrq4f@wobu-vie.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=pbs-devel@lists.proxmox.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.