yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: "Lin Jen-Shin (godfat)" <godfat@godfat.org>
To: Eric Wong <e@80x24.org>
Cc: yahns-public@yhbt.net
Subject: Re: [RFC] proxy_pass: document as public API
Date: Sat, 20 Feb 2016 16:37:03 +0800	[thread overview]
Message-ID: <CAA2_N1s-YwUZtNM+Q1tYxfkdTU+BDsjpR_YYh86i1QFOVmQ9PA@mail.gmail.com> (raw)
In-Reply-To: <20160220081619.GA10850@dcvr.yhbt.net>

On Sat, Feb 20, 2016 at 4:16 PM, Eric Wong <e@80x24.org> wrote:
> We've been using this for nearly a year to serve our own
> list archives using (Apache (mpm_prefork) || Starman) and
> Varnish-cache on: http://yhbt.net/yahns-public/
> ---
>  Any thoughts?  So far I've resisted having a public API.
>  On the other hand, the current state of ProxyPass being a
>  Rack app using rack.hijack still has nasty limitations
>  such as incompatibility with any existing middleware.
>  Something simple such as access logs won't work well
>  (e.g. Rack::CommonLogger or Clogger)

My first impression was that why not put this in a separate
gem, say yahns-apps or so? I am not saying we should do
this, just curious why? Easier to maintain and distribute?

>  On the other hand, it would be nice to have a mostly-Ruby
>  alternative to nginx today...

I am even more curious to this. Nginx is pretty accessible already,
(perhaps not on Windows though?) and it would surely be more
performant than Ruby. Or is it because we might want to make it
not only a reverse proxy, extending it with Rack middleware?
If so, then we probably don't want this directive:


but just treat it as a Rack application? Or we might want to define
another middleware, say proxy_pass's middleware, which would
be slightly different than the rack ones? If so I think it makes a lot
of sense to have app(:proxy_pass).


  reply	other threads:[~2016-02-20  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  8:16 [RFC] proxy_pass: document as public API Eric Wong
2016-02-20  8:37 ` Lin Jen-Shin (godfat) [this message]
2016-02-20  9:41   ` Eric Wong

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:

  List information: https://yhbt.net/yahns/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA2_N1s-YwUZtNM+Q1tYxfkdTU+BDsjpR_YYh86i1QFOVmQ9PA@mail.gmail.com \
    --to=godfat@godfat.org \
    --cc=e@80x24.org \
    --cc=yahns-public@yhbt.net \


* 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.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).